X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=9f976cf2fd99f88f98fb7bf64f54493095ce5ad0;hb=220e61140711138cbab9f1e8e0a04ca4828bab27;hp=15891f81e0fa99333ad81e9271df5b2a72ba368e;hpb=1bd90415deccc4562e0fb4d0f8e58140aa687ac1;p=git.git diff --git a/TODO b/TODO index 15891f81..9f976cf2 100644 --- a/TODO +++ b/TODO @@ -1,95 +1,139 @@ -What to expect after 0.99.5 -=========================== +The GIT To-Do File +================== -This is written in a form of to-do list for me, so if I say -"accept patch", it means I do not currently plan to do that -myself. People interested in seeing it materialize please take -a hint. + The latest copy of this document is found at + http://kernel.org/git/?p=git/git.git;a=blob;hb=todo;f=TODO -Documentation -------------- -* Accept patches from people who actually have done CVS - migration and update the cvs-migration documentation. - Link the documentation from the main git.txt page. +What to expect from now on +========================== -* Update the SubmittingPatches document to add MUA specific - hints on how to disable unwanted MIME and flowed-text by - collecting past list postings. Accept patches from people who - was hit by shiny blue bat to update the same. +This is written in a form of to-do list for me, so if I say +"accept patch", it means I do not currently plan to do that +myself. People interested in seeing it materialize please take +a hint. Also whatever I marked "Perhaps" do not have to happen +if ever -- only if somebody cares enough and submits a clean +patch, perhaps ;-). -* Talk about using rsync just once at the beginning when - initializing a remote repository so that local packs do not - need to be expanded. I personally do not think we need tool - support for this. -* Update tutorial to cover shared repository style a bit more, - maybe with a toy project that involves two or three - repositories. +Design issues +------------- -* Update tutorial to cover setting up repository hooks to do - common tasks. +* tree entries in index? -- sorry, stalled -* Get help to properly use asciidoc in tutorial. +* "intent to add" index entries? -- together with the above + needs rethinking. -* Maybe justify and demonstrate an Octopus in the tutorial. Add - it to the glossary. +* Plug-in file-level merges. On the other hand, we may not even + need this; just tell people to run "xxdiff -U" on the working + tree files (or kompare). Technical (heavier) ------------------- -* Tony Luck reported an unfortunate glitch in the 3-way merge. - Encourage discussions to come up with a not-so-expensive way - to catch the kind of ambiguities that led to his misery. +* Libification. There are many places "run once" mentality is + ingrained in the management of basic data structures, which + need to be fixed. [Matthias Urlichs was already working on + this: , but I + do not know what happened to his efforts] + +* Lazy clones that can be controlled by the user, ranging from + totally on-demand a la CVS/SVN to "cache down to this old + commit so that I can make full use of git on at least recent + history". This need a lot of work in making tools to exit + gracefully when they hit unavailable objects while offline. Technical (milder) ------------------ -* When the branch head pointed by $GIT_DIR/HEAD changes while - the index file and working tree are looking the other way - (e.g. somebody pushed into your repository, or you ran "git - fetch" to update the ref your working tree is on), "git - checkout" without -f gets confused. Figure out a good way to - handle this. +* git grep should be able to omit prefix when invoked from a + subdirectory. Either make it an option or default with + --full-name like ls-files does. + +* duplicated refspec given to "fetch-pack a a a" makes it emit + strange error message because it triggers the "match only + once" logic. Maybe strip the dups on the input side + (Uwe Zeisberger + <20060608073857.GA5072@informatik.uni-freiburg.de>). + +* map only parts of huge packfiles and LRU fragments of them. + People are starting to try git on projects with deep history + and/or many objects, e.g. Mozilla. -* "git commit -m" should work for initial commits and perhaps - merge commits as well. Warning about merge is still a good - thing to do, while -m is useful in scripted non-interactive - use, so we need to be careful. +* upload-pack support for start fetching from any valid point on + the history, not just published refs. (Erik W. Biederman + ) -* Encourage concrete proposals to commit log message templates - we discussed some time ago. +* git-daemon side support for virtual hosting. Client side + is ready in 1.4.0 (Jon Loeliger <1149610100.23938.75.camel@cashmere.sps.mot.com>). -* Bug Ryan and work with him to update send-email easier to use. +* teach git-upload-pack not to ack-continue early when the + client has roots it does not know about but it already has + learned the fork points for all the requested heads + (Ralf Baechle <20060524131022.GA11449@linux-mips.org>). -* Look at portability fixes from Jason Riedy +* Per user .gitconfig across repositories -- ongoing. - http://www.cs.berkeley.edu/~ejr/gits/git.git#portable +* Encourage competition between annotate vs blame. Maybe come + up with some nontrivial test cases. -* Accept patches to cause "read-tree -u" delete a directory when - it makes it empty. +* Subprojects. Try "gitlink" -- sorry, stalled. -* Perhaps accept patches to introduce the concept of "patch flow - expressed as ref mappings" Josef has been advocating about. +* Rebase and checkout -m should be able to use recursive + strategy as well. These commands currently do not work across + renames. -* MIMEified applymbox to grok B and Q encodings in headers and - turn them into UTF-8; unwrap QP; explode multipart. +* Decide what to do about rebase applied to merged head. One + extreme is to allow rebase if "rev-list ours..theirs" gives + anything. This loosens the current merge-base based approach. + The other extreme is to refuse rebase if "rev-list + theirs..ours" contains any merge commit, which was discussed + on the list. + + <43CC695E.2020506@codeweavers.com> + +* Decide what the right thing to do upon an empty merge commit, + when both branches happen to have obtained the same set of + changes through different history. Not recording such keeps + the history simpler, and the next merge would soon create a + true merge commit anyway, but this does not feel quite right. + + <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com> + +* diff stopping at the first output; qgit wants to know if this + tree has any A or D from the other tree and nothing else. + Would help internal tree-diff in rev-list as well. + +* daemon --strict-symlink. + +* daemon --base-path does not apply automatically to whitelist + somehow feels wrong. If somebody cares enough, accept + patches. + +* Perhaps detect cloning request in upload-pack and cache the + result for next cloning request until any of our refs change. + +* Maybe grok PGP signed text/plain in applymbox as well. + + +Technical (trivial) +------------------- -* "git cherry-pick" that applies the patch an existing commit - introduces in its ancestry chain, possibly using the 3-way - merge machinery; update rebase using the cherry-pick command. - Carl's redo/undo might fall out naturally from this. +* git-proxy should be spawned with sh -c 'command' $1 $2. -* A tool to detect, show and prune already merged topic - branches. +* Maybe a true git-proxy command that reads the first request + pkt-line, and redirects the request to its real destination. -* Perhaps "git branch -d" to delete a branch. +* test scripts for the relative directory path stuff. -* Enhance "git repack" to not always use --all; this would be - handy if the repository contains wagging heads like "pu" in - git.git repository. +* In a freshly created empty repository, `git fetch foo:bar` + works OK, but `git checkout bar` afterwards does not (missing + `.git/HEAD`). -* Remove "git clone-dumb-http". + +Local Variables: +mode: text +End: