X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=0d86e47d6c3772347088a80abaa4ddade3d2b72f;hb=0bc1bdd1ec394705a13ec726bd25ad5390746277;hp=15ecb597dbf474058a7071c7db75aa0010941ae9;hpb=c3b9ed08caf84bca24902b3b2750ad61e411da98;p=git.git diff --git a/TODO b/TODO index 15ecb597..0d86e47d 100644 --- a/TODO +++ b/TODO @@ -6,19 +6,8 @@ The GIT To-Do File http://kernel.org/git/?p=git/git.git;a=blob;hb=todo;f=TODO -Tool Renames Plan -================= - - - In 0.99.9, the backward compatible symbolic links in - $(bindir) will be removed. - - git-ssh-push and git-ssh-pull pair is not going away if ever. - Each of these old-name commands continues to invoke its - old-name counterpart on the other end. - - -What to expect after 0.99.8 -=========================== +What to expect from now on +========================== 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 @@ -28,68 +17,55 @@ if ever -- only if somebody cares enough and submits a clean patch, perhaps ;-). -Documentation +UI +-- + +* Make "git branch -d foo" while on foo branch suggest "maybe + you want to go back to 'master'?" + + +Design issues ------------- -* Document the ref naming restrictions [DONE]. +* "intent to add" index entries? -* David Ho's report suggests whatchanged documentation should - mention -m as "commonly used options". Steal Linus' - response [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. -* Help Jon Loeliger to find place in the documentation to place - his drawing. +* Doing a merge in a separate directory? -* 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. +* Make 'format-patch' take revision limiters similar to + rev-list. For example: -* 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). + A C + ....---x---o---o---x---o---o + / + / + / + ....---x---o---o + B -* Maybe update tutorial with a toy project that involves two or - three developers.. + we should be able to format commits 'o', without duplicates, + by: -* Update tutorial to cover setting up repository hooks to do - common tasks. + $ git format-patch ^A ^B C -* Do we still have missing docs? If so accept patches to finish - them. + Currently the closest approximation is -* Accept patches to talk about "Whoops, it broke. What's - next?". + $ git format-patch A..C B..C -* Accept patches to make formatted tables in asciidoc to work - well in both html and man pages (see git-diff(1)). + which results in the last two commits including C formatted + twice. Technical (heavier) ------------------- -* 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. [DONE; git-index-pack by Sergey, - tweaking clone by me] - -* Git daemon, when deployed at kernel.org, might turn out to be - quite a burden, since it needs to generate customized packs - every time a new request comes in. It may be worthwhile to - precompute some packs for popular sets of heads downloaders - have and serve that, even if that could give more than the - client asks for in some cases. We will know about this soon - enough [DONE part to allow using precomputed pack, but not - dynamic caching part]. - * Libification. There are many places "run once" mentality is ingrained in the management of basic data structures, which need to be fixed. [Matthias Urlichs is already working on - this: ; Post - 1.0]. + this: ] * Maybe a pack optimizer. @@ -101,190 +77,67 @@ Technical (heavier) closely, (3) somebody who tends to follow only the point releases. -* Maybe an Emacs VC backend. - -* 'git split-projects'? This requires updated 'git-rev-list' to - skip irrelevant commits. - Message-ID: - -* Look at libified GNU diff CVS seems to use, or libxdiff. - [Daniel has his own diff tool almost ready to start - integrating and testing; Post 1.0] - -* Accept patches to fetch multiple objects by HTTP in parallel. - [DONE] - -* Plug-in file-level merges [Post 1.0]. - -* Per-repository configuration mechanism [DONE by Linus]. + This needs a matching smart on the dumb protocol downloader. Technical (milder) ------------------ -* Merlyn reports trouble with http fetch [Hopefully solved by - Nick's updates]. - -* Maybe look at Cogito and see if I can help Pasky to adjust to - the later core features? Zack Brown's "cg-seek leaving empty - directories" problem is a good example of this. - -* Perhaps detect cloning request in upload-pack and cache the - result for next cloning request until any of our refs change. - -* Perhaps accept more "want"s in upload-pack and do something - intelligent about it [Ongoing, by Johannes]. +* Shallow clones. -* Perhaps send less "want"s from fetch-pack [DONE by JS]. +* Encourage competition between annotate vs blame. Maybe come + up with some nontrivial test cases. -* Look at svn importer Smurf has. There is a small cvsimport - update in his tree as well [DONE]. +* Subprojects. I think the "bind commit" approach has been + outlined at sufficiently detailed level. Maybe find time to + actually start prototyping it? -* Decide the notation of "peeling the onion" operator, and - implement it in sha1_name.c. Perhaps postfix "^{}" to mean - "peel and expect anything", "^{blob}" to mean "peel and barf - unless blob". The current "^0" becomes shorthand for - "^{commit}". [DONE] + <7vacdzkww3.fsf@assigned-by-dhcp.cox.net> -* Quote the URL so that libcurl's metecharacter mechanism would - not kick in [DONE]. +* 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. -* Review the Makefile variables and exporting rules for them, - while looking at prefix passing by Kai Ruemmler [DONE]. + <43CC695E.2020506@codeweavers.com> -* Review the 'sparse object database' change by Linus and move - the first phase of it to the "master" branch [DONE]. +* 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. -* Decide on mmap(). I am inclined to just stick to mmap - replacement by Johannes Schindelin and do nothing else right - now, except perhaps drop the writing-back support [DONE]. + <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com> -* Revisit Santi's patch to move commit temorary files out of the - working tree toplevel [DONE]. +* 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. -* More generally, review the use of temporary files again. - Assuming writable $GIT_DIR is more acceptable, but the - working tree toplevel may not be in a rare usage pattern. +* daemon --strict-symlink. -* Encourage concrete proposals to commit log message templates - we discussed some time ago. +* daemon --base-path does not apply automatically to whitelist + somehow feels wrong. If somebody cares enough, accept + patches. -* Accept patches to cause "read-tree -u" delete a directory when - it makes it empty [DONE]. - -* Perhaps accept patches to do undo/redo. - -* Perhaps accept patch to optionally allow '--fuzz' in - 'git-apply'. - -* Allow 'git apply' to accept GNU diff 2.7 output that forgets - to say '\No newline' if both input ends with incomplete - lines. - -* What to do with TABs and LFs in pathnames without breaking GNU - patch? [DONE -- go with GNU patch extension proposed by Paul]. - -* Adjust apply.c to proposed GNU patch extension that quotes \n - and \t in C style, inside "". [DONE] +* Perhaps detect cloning request in upload-pack and cache the + result for next cloning request until any of our refs change. -* Adjust diff.c to the same. [DONE] +* Perhaps deal with "Files differ" (binary diff) in non C + locales. * Maybe grok PGP signed text/plain in applymbox as well. -* Perhaps a tool to revert a single file to pre-modification - state? People with BK background know this operation as - 'clean'. 'git checkout [-f] ent [path...]' was suggested by - Matthias Urlichs which sounds a natural extention to what the - command currently does [DONE with a prodding by Linus]. - -* Enhance "git repack" to not always use --all; this would be - handy if the repository contains wagging heads like "pu" in - git.git repository. - -* Make rebase restartable; instead of skipping what cannot be - automatically forward ported, leave the conflicts in the work - tree, have the user resolve it, and then restart from where it - left off [mechanism mostly done]. - -* Output full path in the "git-rev-list --objects" output, not - just the basename, and see the improved clustering results in - better packing [Tried, but did not work out well]. - -* Updated git-changes-script Jeff Garzik needs [Inquiry for - external spec sent out with a quick hack. Will know if that - is what he needs hopefully soon]. - -* An mechanism to ignore filesystem mode bits altogether [DONE]. - Technical (trivial) ------------------- -* Peter Hagervall's sparse fix [DONE]. - -* Alex Riesen reported that hooks are in effect in tests. - Should fix [DONE]. - -* Disallow [\001-\040\177] byte values from ref names. Also we - need to disallow ':' (used in refspec), '^' and '~' (postfix - "peel the onion" operators), and '..' ("ref1..ref2" notation - becomes ambiguous otherwise) [DONE]. - -* Update fetch-pack and clone-pack to ignore funny refs from the - other end, while making sure peek-remote does not discard them. - [DONE] - -* Update upload-pack to send tag^{}. This would hopefully help - Pasky's automated tag tracking, and also Martin's findtags. - [DONE] - -* Adjust update-index to quoted --index-info [DONE]. - -* Prepare apply.c changes for maint branch (0.99.8e) [DONE]. - -* Perhaps show ^{commit}, ^{tree} instead of ^{} from ls-remote? [NO] - -* Re-adjust maint branch for the above if we did so. [NOT NEEDED] - -* short SHA1 naming is not enforcing uniqueness. Should fix [DONE]. - -* 'git repack' can be DOSed. Should fix [DONE]. - -* Stop installing the old-name symlinks [IN 0.99.9]. - -* 'git merge-projects'? - - Subject: Re: Merges without bases - References: <1125004228.4110.20.camel@localhost.localdomain> - Date: Thu, 25 Aug 2005 15:26:36 -0700 - Message-ID: <7vvf1tps9v.fsf@assigned-by-dhcp.cox.net> - -* 'git lost-and-found'? Link dangling commits found by - fsck-objects under $GIT_DIR/refs/lost-found/. Then - show-branch or gitk can be used to find any lost commit. [A - feeler patch sent out. Very underwhelming response X-<.] - - Do not name it /lost+found/; that would probably confuse - things that mistake it a mount point (not our code but - somebody else's). - -* Add simple globbing rules to git-show-branch so that I can - say 'git show-branch --heads "ko-*"' (ko-master, ko-pu, and - ko-rc are in refs/tags/). - -* 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: +* git-proxy should be spawned with sh -c 'command' $1 $2. - git-update-index - git-ls-files - git-diff-files - git-diff-index - git-diff-tree - git-rev-list - git-rev-parse +* test scripts for the relative directory path stuff. -* In a freashly created empty repository, `git fetch foo:bar` +* In a freshly created empty repository, `git fetch foo:bar` works OK, but `git checkout bar` afterwards does not (missing `.git/HEAD`).