X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=4135038fb326afa1e3568487ff680b2066e56927;hb=4ec53b6fb6f7454e45a561d6a62fd4e45e0cd2e9;hp=6544209066a3cebb5d1ad91ca4ef50adff52ccaf;hpb=13217fc0c90902acf57cc94fa37f5c3ef06b619b;p=git.git diff --git a/TODO b/TODO index 65442090..4135038f 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,57 +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. +Design issues +------------- -* Accept patches to finish missing docs. +* 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) ------------------- -* 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. - * 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. @@ -95,62 +63,57 @@ 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. - [DONE] - -* Plug-in file-level merges [Post 1.0]. - -* Per-repository configuration mechanism [DONE by Linus]. + integrating and testing] Technical (milder) ------------------ -* 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]. +* send-pack/receive-pack protocol updates, to allow the receiver + to report what it did to the ref update requests. -* Review the 'sparse object database' change by Linus and move - the first phase of it to the "master" branch [DONE]. +* Perhaps a smarter HTTP anonymous download via CGI. -* 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]. +* 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. -* Revisit Santi's patch to move commit temorary files out of the - working tree toplevel [DONE]. +* Forbid/ignore pack names that do not conform to the convention + sha1_pack_name() assumes and reject in check_packed_git_idx() + [In pu] -* 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. +* strip leading directory from ls-tree output, to match ls-files + output. -* Perhaps accept more "want"s in upload-pack and do something - intelligent about it. + 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. -* Perhaps detect cloning request in upload-pack and cache the - result for next cloning request until any of our refs change. + [We should not do this, or do this carefully, if we were to + merge the "git-checkout (--|) work from + subdirectory" patch.] -* Perhaps send less "want"s from fetch-pack. +* 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. -* Encourage concrete proposals to commit log message templates - we discussed some time ago. +* 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. -* Accept patches to cause "read-tree -u" delete a directory when - it makes it empty [DONE]. +* daemon --strict-symlink. -* Perhaps accept patches to do undo/redo. +* 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'. @@ -159,96 +122,30 @@ 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? [Have patch in proposed updates. Discussion still - ongoing with Paul.] +* 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 [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) ------------------- -* Disallow [\001-\040\177] byte values from ref names. Also we - need to disallow ':' (used in refspec), '^' and '~' (postfix - "peel the onion" operators) and leading '+' (again used in - refspec, as prefix "force update" operator) [DONE]. +* Versioning scheme. The next maintenance installment will be + 1.0.3 not 1.0.0c. The next feature release would be 1.1.0. -* 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/). +* Either drop supporting Debian myself or coerce patches out of + the official maintainer. * 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`).