X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=d7503d28751b733ad6adae1c43f77ccd71058e5f;hb=7442ed29c778e1e1a2f0c1cf0057207d9f319a0c;hp=6f5191933b44756036ea83d3b13379128ffc9141;hpb=7b5f821775fbc6925c8aeff1b2643cd62ea19cff;p=git.git diff --git a/TODO b/TODO index 6f519193..d7503d28 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 -================= - - - Immedately after 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.9 -=========================== +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 @@ -31,51 +20,38 @@ patch, perhaps ;-). Documentation ------------- -* Help Jon Loeliger to find place in the documentation to place - his drawing. - -* 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. - * 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). * 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. -* Do we still have missing docs? If so accept patches to finish - them. +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. -* Accept patches to talk about "Whoops, it broke. What's - next?". +* 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.] -* Accept patches to make formatted tables in asciidoc to work - well in both html and man pages (see git-diff(1)). +* Perhaps "everything in config file"? Especially remotes/ + shortcuts. I am modestly negative about this. Technical (heavier) ------------------- -* 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. @@ -87,33 +63,55 @@ 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] - -* Plug-in file-level merges [Post 1.0]. + integrating and testing] Technical (milder) ------------------ -* 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. +* send-pack/receive-pack protocol updates, to allow the receiver + to report what it did to the ref update requests [DONE]. -* Perhaps detect cloning request in upload-pack and cache the - result for next cloning request until any of our refs change. +* Perhaps a smarter HTTP anonymous download via CGI. + +* Prepare to enable "always use symbolic refs for HEAD" patch. + We need a timeline to force Porcelains to get ready. Last + time I looked at them I got an impression that gitweb was not + ready. -* Encourage concrete proposals to commit log message templates - we discussed some time ago. +* Forbid/ignore pack names that do not conform to the convention + sha1_pack_name() assumes and reject in check_packed_git_idx() + [In pu] -* Perhaps accept patches to do undo/redo. +* strip leading directory from ls-tree output, to match ls-files + output. + + I am of two minds about this one. diff output must always be + -p1 format no matter where the command was started, and + ls-tree might be easier to use if it matched diff, not + ls-files. + + [DONE, with --full-name option like ls-files] + +* 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. + +* 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. + +* daemon --strict-symlink. + +* 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'. @@ -122,64 +120,39 @@ Technical (milder) to say '\No newline' if both input ends with incomplete lines. -* Maybe grok PGP signed text/plain in applymbox as well. - -* Enhance "git repack" to not always use --all; this would be - handy if the repository contains wagging heads like "pu" in - git.git repository. +* Perhaps deal with "Files differ" (binary diff) in non C + locales. -* 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]. +* Maybe grok PGP signed text/plain in applymbox as well. * 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]. +* Daemon --base-path does not apply automatically to whitelist + somehow feels wrong. If somebody cares enough, accept + patches. Technical (trivial) ------------------- -* Stop installing the old-name symlinks [IN 0.99.9]. +* Daemon --base-path forbidding user-path automatically feels + wrong. If somebody cares enough, accept patches. -* 'git merge-projects'? +* git-proxy should be spawned with sh -c 'command' $1 $2. - 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> +* Versioning scheme. The next maintenance installment will be + 1.0.3 not 1.0.0c. The next feature release would be 1.1.0 [DONE]. -* '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/). +* Either drop supporting Debian myself or coerce patches out of + the official maintainer [DONE -- DROPPED]. * 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 - -* In a freashly created empty repository, `git fetch foo:bar` + stuff Linus has been working on. Most of the C-level + commands should be usable with relative directory paths. + +* In a freshly created empty repository, `git fetch foo:bar` works OK, but `git checkout bar` afterwards does not (missing `.git/HEAD`).