X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=a1dd9285a02329f604361ed326ca9d45207a654f;hb=18ea0bf72c0fce404e0ff3f9489b29e8dcc8beea;hp=73a4cf356e40e60daf371ae880b5d074cd4aed01;hpb=fd2b323def3ad40b0e85105321d06bad3ff36d58;p=git.git diff --git a/TODO b/TODO index 73a4cf35..a1dd9285 100644 --- a/TODO +++ b/TODO @@ -6,21 +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.8, we will still install the backward compatible - symbolic links in $(bindir). These will however be removed - before 1.0 happens. - - git-ssh-push and git-ssh-pull pair is not going away within - this timeframe, 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 @@ -33,56 +20,56 @@ patch, perhaps ;-). Documentation ------------- -* Help Jon Loeliger to find place in the documentation to place - his drawing. +* Take the updated tutorial by Bruce Fields very seriously. It + is a quite good initiative. + + +Design issues +------------- + +* 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. + +* Doing a merge in a separate directory. + +* Subprojects. I think the "bind commit" approach has been + outlined at sufficiently detailed level. Maybe find time to + actually start prototyping it? -* 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. + <7vacdzkww3.fsf@assigned-by-dhcp.cox.net> -* 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). +* Make 'format-patch' take revision limiters similar to + rev-list. For example: -* Maybe update tutorial with a toy project that involves two or - three developers.. + A C + ....---x---o---o---x---o---o + / + / + / + ....---x---o---o + B -* Update tutorial to cover setting up repository hooks to do - common tasks. + we should be able to format commits 'o', without duplicates, + by: -* Accept patches to finish missing docs. + $ git format-patch ^A ^B C -* Accept patches to talk about "Whoops, it broke. What's - next?". + Currently the closest approximation is -* Accept patches to make formatted tables in asciidoc to work - well in both html and man pages (see git-diff(1)). + $ git format-patch A..C B..C + + 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. - -* 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. - * 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. @@ -94,146 +81,98 @@ Technical (heavier) closely, (3) somebody who tends to follow only the point releases. -* Maybe an Emacs VC backend. + This needs a matching smart on the dumb protocol downloader. -* 'git split-projects'? This requires updated 'git-rev-list' to - skip irrelevant commits. - Message-ID: +* Maybe an Emacs VC backend. * 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. - [Preferably before 1.0] - -* Plug-in file-level merges [Post 1.0]. + integrating and testing] Technical (milder) ------------------ -* Review the Makefile variables and exporting rules for them, - while looking at prefix passing by Kai Ruemmler. +* 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 'sparce object database' change by Linus and move - the first phase of it to the "master" branch. + <43CC695E.2020506@codeweavers.com> -* Decide on mmap(). I am inclined to just stick to mmap - replacement by Johannes Schindelin and do nothing else right - now. +* 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 does not feel quite right. -* Revisit Santi's patch to move commit temorary files out of the - working tree toplevel. More generally, review the use of - temporary files again. Assuming $GIT_DIR is writable is - more acceptable, but the working tree toplevel may not be in - a rare usage pattern. + <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com> -* Perhaps accept more "want"s in upload-pack and do something - intelligent about it. +* Perhaps a smarter HTTP anonymous download via CGI. -* Perhaps detect cloning request in upload-pack and cache the - result for next cloning request until any of our refs change. +* Prepare to enable "always use symbolic refs for HEAD" patch. + We need a timeline to force Porcelains to get ready. All the + major ones should be ready now. + +* Prepare to enable "most of the things are installed in + GIT_EXEC_PATH not in bindir". I do not plan to set bindir != + gitexecdir myself in the main Makefile I ship, but distos + should be able to choose to do so. -* Perhaps send less "want"s from fetch-pack. +* Forbid/ignore pack names that do not conform to the convention + sha1_pack_name() assumes and reject in check_packed_git_idx() + [In "pu"] -* Encourage concrete proposals to commit log message templates - we discussed some time ago. +* Any Porcelain-ish we forgot or punted to make usable from + subdirectory? I think the last pass caught everything and + what are remaining are whole-tree or whole repository + operations. -* Accept patches to cause "read-tree -u" delete a directory when - it makes it empty. +* 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. -* Perhaps accept patches to do undo/redo. +* daemon --strict-symlink. + +* daemon --no-user-dir, to make ~user still work with + --base-path. They ought to be independent. + +* 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. * Perhaps accept patch to optionally allow '--fuzz' in - 'git-apply'. + 'git-apply'. am/applymbox is _not_ the place to do it. * 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? +* 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. - -* Enhance "git repack" to not always use --all; this would be - handy if the repository contains wagging heads like "pu" in - git.git repository. - -* 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. - - The point is to make it possible to fork that part off to - somebody else; then I do not have to maintain Documentation - directory myself anymore, just like I simply slurp the latest - gitk from Paul and not worry about it ;-). - -* 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. - * 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 soon enough]. - Technical (trivial) ------------------- -* short SHA1 naming is not enforcing uniqueness. Should fix [DONE]. - -* 'git repack' can be DOSed. Should fix [DONE]. - -* Stop installing the old-name symlinks [POSTPONED, but before 1.0]. - -* '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/). +* s/naked/bare/g. -* 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`).