X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=62020893988b141c4a4088c109fa65898812e13d;hb=52dd75885cd3a78dcb3d7f4f0ddf16f4b8f62b56;hp=20dfbd09a43d37da2c6b28af64ad78f8b6366067;hpb=27442c64acd1f12e613a6a5c59c4d476df584160;p=git.git diff --git a/TODO b/TODO index 20dfbd09..62020893 100644 --- a/TODO +++ b/TODO @@ -6,26 +6,17 @@ 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 until 1.0 +======================== 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. +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 ;-). + +Only handful things remain until 1.0. Documentation @@ -41,66 +32,85 @@ 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. -* Accept patches to finish missing docs. +* Do we still have missing docs? If so accept patches to finish + them. * Accept patches to talk about "Whoops, it broke. What's - next?". + next?" [ONGOING]. * Accept patches to make formatted tables in asciidoc to work well in both html and man pages (see git-diff(1)). +* Work around multiple synopses lines in manual pages + (e.g. git-bisect). + 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. + need to be fixed. [Matthias Urlichs is already working on + this: ; Post + 1.0]. * Maybe a pack optimizer. -* Maybe an Emacs VC backend. + Given a set of objects and a set of refs (probably a handful + branch heads and point release tags), find a set of packs to + allow reasonably minimum download for all of these classes of + people: (1) somebody cloning the repository from scratch, (2) + somebody who tends to follow the master branch head reasonably + closely, (3) somebody who tends to follow only the point + releases. + + 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] + +* Plug-in file-level merges [Post 1.0]. On the other hand, we + may not even need this; just tell people to run "xxdiff -U" on + the working tree files. + +* Ref namespace management. Perhaps use refs/local/ suggestion + by Linus. [Does not seem to be high on people's priority list, + and not interested myself. People can resurrect this + discussion if they want.] Technical (milder) ------------------ -* Encourage concrete proposals to commit log message templates - we discussed some time ago. +* strip leading directory from ls-tree output. + +* 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 [can be post + 1.0]. -* Accept patches to cause "read-tree -u" delete a directory when - it makes it empty. +* merge-recursive needs to register conflicting paths as higher + stage entries in the index. For that, it first needs to + construct three trees whose paths are already renamed, and + call 3-way read-tree. Alternatively, update-index needs to + give it a way to construct higher stages [can be post 1.0, but + nicer to have in 1.0]. -* Perhaps accept patches to introduce the concept of "patch flow - expressed as ref mappings" Josef has been advocating about. +* daemon --strict-symlink [can be post 1.0]. -* Perhaps accept patches to do undo/redo. +* Binary package split. Plan laid out and discussion mostly + done. [RPM side done; Debian side thrown over the wall.] + +* 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'. @@ -111,71 +121,21 @@ Technical (milder) * 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. - -* 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. - -* 'git repack' can be DOSed. Should fix. - -* Stop installing the old-name symlinks [POSTPONED]. - -* 'git merge-projects'? - -* '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-update-index - git-ls-files - git-diff-files - git-diff-index - git-diff-tree - git-rev-list - git-rev-parse + stuff Linus has been working on. Most of the C-level + commands should be usable with relative directory paths. * In a freashly created empty repository, `git fetch foo:bar` works OK, but `git checkout bar` afterwards does not (missing