X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=9f976cf2fd99f88f98fb7bf64f54493095ce5ad0;hb=48d2c0e21f19c0a771492428cdf7f274536e8ae0;hp=66c4bd77c1d1fe99886d87a5821d09f117427947;hpb=1d2cd55abc53201a5686d0e85879eda6b25dc9ad;p=git.git diff --git a/TODO b/TODO index 66c4bd77..9f976cf2 100644 --- a/TODO +++ b/TODO @@ -1,219 +1,137 @@ -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. - - -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. - -* Link howto docs from the git.txt page. [DONE] - -* Update the SubmittingPatches document to add MUA specific - hints on how to disable unwanted MIME and flowed-text by - collecting past list postings [DONE]. + The latest copy of this document is found at -* Accept patches from people who were hit by shiny blue bat to - update the SubmittingPatches [ONGOING]. + http://kernel.org/git/?p=git/git.git;a=blob;hb=todo;f=TODO -* 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 (but see below about optimized cloning). -* Review the existing docs and see if the repository - organization needs to be clarified further [DONE]. +What to expect from now on +========================== -* Update tutorial to cover shared repository style a bit more - [DONE]. - -* Maybe update tutorial with a toy project that involves two or - three developers.. +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 ;-). -* Document the hooks [DONE]. -* Update tutorial to cover setting up repository hooks to do - common tasks. +Design issues +------------- -* Get help to properly use asciidoc in tutorial [Heck, ended up - learning it myself, DONE]. +* tree entries in index? -- sorry, stalled -* Maybe justify and demonstrate an Octopus in the tutorial - [STILL NEEDSWORK]. +* "intent to add" index entries? -- together with the above + needs rethinking. -* Add Octopus to the glossary [Thanks Johannes, DONE]. +* 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. - [Daniel's patch looks quite promising.] - -* HPA has two projects, klibc and klibc-kbuild, that have large - set of overlapping files in different paths (i.e. one has many - renames from the other). There currently is no way for git to - help keep these two trees in sync, merging criss-cross between - them. The merge logic should be able to take advantage of - rename/copy detection smarts git-diff-* family has [Discussion - ongoing]. - -* We might want to optimize cloning with GIT native transport - not to explode the pack, and store it in objects/pack instead. - We would need a tool to generate an idx file out of a pack - file for this. Also this itself may turn out to be a bad - idea, making the set of packs in repositories everybody has - different from each other. - -* Maybe a pack optimizer. I am not convinced that packing all - objects into a single pack and removing all the existing panck - is the right way to go, since that would work against people - who already have those packs. +* 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] -* Maybe an Emacs VC backend. +* 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. [DONE] +* 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. -* We still have the same issue with "git fetch". Fetching into - the branch one is on _may_ need to do the same thing as - fetching into anonymous head and then do the resolve. At - least it needs a warning. [DONE] +* 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>). -* "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. [DONE] +* 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. -* Encourage concrete proposals to commit log message templates - we discussed some time ago. +* upload-pack support for start fetching from any valid point on + the history, not just published refs. (Erik W. Biederman + ) -* Test apply.c patches from Robert Fitzsmons and have them - graduate to "master" branch [IN PROGRESS]. +* 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>). -* Test read-tree reorganization patches from Daniel and have - them graduate to "master" branch [TESTED]. +* 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>). -* Bug Ryan and work with him to update send-email easier to use. - [Ryan's patch pushed into "master". Will see how well it is - accepted.] +* Per user .gitconfig across repositories -- ongoing. -* Look at portability fixes from Jason Riedy +* Encourage competition between annotate vs blame. Maybe come + up with some nontrivial test cases. - http://www.cs.berkeley.edu/~ejr/gits/git.git#portable +* Subprojects. Try "gitlink" -- sorry, stalled. - [Applied. Burned by one of them and backed out, but otherwise - looks OK.] +* Rebase and checkout -m should be able to use recursive + strategy as well. These commands currently do not work across + renames. -* Accept patches to cause "read-tree -u" delete a directory when - it makes it empty. +* 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. -* Perhaps accept patches to introduce the concept of "patch flow - expressed as ref mappings" Josef has been advocating about. + <43CC695E.2020506@codeweavers.com> -* Perhaps accept patches to do undo/redo. +* 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. -* MIMEified applymbox to grok B and Q encodings in headers and - turn them into UTF-8; unwrap QP; explode multipart. [DONE] + <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com> -* Maybe grok PGP signed text/plain in applymbox as well. - -* Perhaps a tool to revert a single file to pre-modification - state? git-cat-file blob `git-ls-files | grep foo` >foo or - git-cat-file blob `git-ls-tree HEAD foo` >foo? What should - the command be called? git-revert is taken so is - git-checkout. - -* "git cherry-pick" that applies the patch an existing commit - introduces in its ancestry chain, possibly using the 3-way - merge machinery. [DONE] - -* Update rebase using the cherry-pick command. [DONE] - -* Redo "git revert" using 3-way merge machinery. [DONE] - -* A tool to detect, show and prune already merged topic - branches. - -* Set up an automated documentation rebuilding procedure at - kernel.org, using update hook mechanism. [DONE] - -* Describe automated documentation rebuilding in a howto form - [DONE]. - -* Enhance "git repack" to not always use --all; this would be - handy if the repository contains wagging heads like "pu" in - git.git repository. +* 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. -* Accept and apply "git repack --all" patch, except the part - that removes the existing packs. [DONE] +* daemon --strict-symlink. -* Internally split the project into non-doc and doc parts; add - an extra root for the doc part and merge from it; move the - internal doc source to a separate repository, like the +Meta - repository; experiment if this results in a reasonable - workflow, and document it in howto form if it does. +* daemon --base-path does not apply automatically to whitelist + somehow feels wrong. If somebody cares enough, accept + patches. -* Add names to all nodes in show-branch [DONE]. +* Perhaps detect cloning request in upload-pack and cache the + result for next cloning request until any of our refs change. -* Option to limit rename detection for more than N paths. - -* Tool renames. [Discussion almost concluded, scheduled to - happen 0.99.7 with backward compatibility links, removing them - in 0.99.8.] +* Maybe grok PGP signed text/plain in applymbox as well. Technical (trivial) ------------------- -* Look at and merge Debian fixes from Tommi [Done]. - -* Perhaps "git branch -d" to delete a branch. - -* Remove "git clone-dumb-http" [DONE]. - -* We would want test scripts for the relative directory path - stuff Linus has been working on. So far, the following - commands should be usable with relative directory paths: - - update-cache - ls-files - diff-files - diff-cache - diff-tree - rev-list - rev-parse - - -Initial repository Gotchas --------------------------- +* git-proxy should be spawned with sh -c 'command' $1 $2. -* `git fetch foo:bar` works OK, but `git checkout bar` - afterwards does not (missing `.git/HEAD`). - -* `git commit -s` did not add signoff for initial commit [DONE]. +* Maybe a true git-proxy command that reads the first request + pkt-line, and redirects the request to its real destination. -* `git status` does not work well when missing `.git/HEAD` [DONE]. +* test scripts for the relative directory path stuff. -* `git log` either; git-log-script uses die which does not exist - [DONE]. +* In a freshly created empty repository, `git fetch foo:bar` + works OK, but `git checkout bar` afterwards does not (missing + `.git/HEAD`). Local Variables: