X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=ca8b5d451ce326125d9d18ae845b1a3dc3534b49;hb=73610e157caf81b478793919987c8e0abd8af949;hp=15ecb597dbf474058a7071c7db75aa0010941ae9;hpb=c3b9ed08caf84bca24902b3b2750ad61e411da98;p=git.git diff --git a/TODO b/TODO index 15ecb597..ca8b5d45 100644 --- a/TODO +++ b/TODO @@ -9,15 +9,15 @@ The GIT To-Do File Tool Renames Plan ================= - - In 0.99.9, the backward compatible symbolic links in - $(bindir) will be removed. + - Immedately after 0.99.9, the backward compatible symbolic + links in $(bindir) will be removed [DONE]. 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 after 0.99.9 =========================== This is written in a form of to-do list for me, so if I say @@ -31,14 +31,8 @@ patch, perhaps ;-). Documentation ------------- -* Document the ref naming restrictions [DONE]. - -* David Ho's report suggests whatchanged documentation should - mention -m as "commonly used options". Steal Linus' - response [DONE]. - * Help Jon Loeliger to find place in the documentation to place - his drawing. + his drawing [DONE]. * Accept patches from people who actually have done CVS migration and update the cvs-migration documentation. @@ -50,7 +44,7 @@ Documentation support for this (but see below about optimized cloning). * Maybe update tutorial with a toy project that involves two or - three developers.. + three developers. * Update tutorial to cover setting up repository hooks to do common tasks. @@ -59,7 +53,7 @@ Documentation them. * Accept patches to talk about "Whoops, it broke. What's - next?". + next?" [Started]. * Accept patches to make formatted tables in asciidoc to work well in both html and man pages (see git-diff(1)). @@ -68,13 +62,14 @@ Documentation 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] +* Assess the side effects of "make the rest of the things + magically work from any subdirectory" change by Linus. It is + a good change in principle and we would like to have that + behaviour but some tool implementations I am sure are assuming + to never run from anywhere other than the top. + +* Ref namespace management. Perhaps use refs/local/ suggestion + by Linus. * Git daemon, when deployed at kernel.org, might turn out to be quite a burden, since it needs to generate customized packs @@ -111,19 +106,18 @@ Technical (heavier) [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]. - Technical (milder) ------------------ -* Merlyn reports trouble with http fetch [Hopefully solved by - Nick's updates]. +* Binary package split. Plan laid out and discussion mostly + done. + +* User-relative paths by Andreas Ericsson. + +* Proxing git:// connection by Paul Collins. * 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 @@ -132,46 +126,9 @@ Technical (milder) * 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]. - -* Perhaps send less "want"s from fetch-pack [DONE by JS]. - -* Look at svn importer Smurf has. There is a small cvsimport - update in his tree as well [DONE]. - -* 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] - -* Quote the URL so that libcurl's metecharacter mechanism would - not kick in [DONE]. - -* Review the Makefile variables and exporting rules for them, - while looking at prefix passing by Kai Ruemmler [DONE]. - -* Review the 'sparse object database' change by Linus and move - the first phase of it to the "master" branch [DONE]. - -* 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]. - -* Revisit Santi's patch to move commit temorary files out of the - working tree toplevel [DONE]. - -* 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. - * Encourage concrete proposals to commit log message templates we discussed some time ago. -* 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 @@ -181,22 +138,8 @@ Technical (milder) 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] - -* Adjust diff.c to the same. [DONE] - * 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. @@ -214,43 +157,14 @@ Technical (milder) 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]. +* Make sure we do reasonable thing on binary files even in + cherry-pick and rebase. 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]. +* Stop installing the old-name symlinks [DONE]. * 'git merge-projects'?