X-Git-Url: https://git.octo.it/?a=blobdiff_plain;f=TODO;h=164398f962f723a59f01a9324f37d2ddae63379e;hb=7b834376cd9138cd92c1cbd0fad1385c9218c20a;hp=85494f9f5780011d09600834e5d7303a0ab6ee6a;hpb=d30a8038bcd5f4d478f75f9f3a7ff01d152d00c6;p=git.git diff --git a/TODO b/TODO index 85494f9f..164398f9 100644 --- a/TODO +++ b/TODO @@ -1,57 +1,31 @@ -What to expect after 0.99.6 -=========================== +The GIT To-Do File +================== -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. The latest copy of this document is found at + The latest copy of this document is found at http://kernel.org/git/?p=git/git.git;a=blob;hb=todo;f=TODO -Tool Renames Plan ------------------ - - - All non-binary commands will lose -script suffix in - $(bindir). The source to git-foo will be either git-foo.sh - or git-foo.perl in the source tree, and the documentation - will be in Documentation/git-foo.txt. - - The commands whose names have 'cache' to mean 'index file' - will get 'cache' in their names replaced with 'index'. For - git-fsck-cache and git-convert-cache, 'cache' will be - replaced with 'objects'. - - - The commit walkers will have 'pull' in their names replaced - with 'fetch'. 'git-ssh-push' will become 'git-ssh-upload'. - - - We continue to follow the convention to name the C source - file that contains the main program of 'git-foo' command - 'foo.c'. That means we will have 'fsck-objects.c', for - example. +Tool Renames Plan +================= - - At this moment, I am not planning to rename the symbols used - in programs, nor any library sources. "cache.h" will stay - "cache.h", so does "read-cache.c". "struct cache_entry" and - "ce_match_stat()" will keep their names. We _might_ want to - rename them in later rounds but not right now. + - In 0.99.8, we will still install the backward compatible + symbolic links in $(bindir). These will however be removed + before 1.0 happens. - - In 0.99.7, all renamed commands will have symbolic links in - $(bindir) so that old names continue to work. These backward - compatible symlinks will not be present in documentation, - though. Especially, the main documentation, git(7) will talk - about the new names. Old environment names defined in - gitenv() will also be removed in this release. + 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. - Tentatively we aim to do this on Sep 17th. - - In 0.99.8, we do not install these backward compatible - symbolic links in $(bindir) anymore. The Makefile will have - a target to remove old symlinks from $(DESTDIR)$(bindir) you - can run manually to help you clean things up. +What to expect after 0.99.8 +=========================== - The timeframe for this is around Oct 1st, but I could be - talked into delaying the symlink removal if Porcelain people - find this schedule too tight. +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. Documentation @@ -61,9 +35,6 @@ Documentation migration and update the cvs-migration documentation. Link the documentation from the main git.txt page. -* Accept patches from people who were hit by shiny blue bat to - update the SubmittingPatches. - * 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 @@ -77,29 +48,16 @@ Documentation * Accept patches to finish missing docs. +* Accept patches to talk about "Whoops, it broke. What's + next?". + +* Accept patches to make formatted tables in asciidoc to work + well in both html and man pages (see git-diff(1)). + Technical (heavier) ------------------- -* Tony Luck reported an unfortunate glitch in the 3-way merge. - Encourage discussions to come up with a not-so-expensive way - to catch the kind of ambiguities that led to his misery. - [Daniel's patch looks quite promising, so is the one from - Fredrik.] - -* HPA has two projects, klibc and klibc-kbuild, that have large - set of overlapping files in different paths (i.e. one has many - renames from the other). There currently is no way for git to - help keep these two trees in sync, merging criss-cross between - them. The merge logic should be able to take advantage of - rename/copy detection smarts git-diff-* family has. Linus, - me, and Daniel outlined a smarter merge strategy for this. - Try them out. - -* To make it easier to experiment with different merge - strategies, make git-merge driver that will run merge backends - for the best merge [tested and in proposed updates]. - * 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 @@ -107,40 +65,43 @@ Technical (heavier) idea, making the set of packs in repositories everybody has different from each other. -* Maybe a pack optimizer. +* 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. -* Maybe an Emacs VC backend. +* Libification. There are many places "run once" mentality is + ingrained in the management of basic data structures, which + need to be fixed. +* Maybe a pack optimizer. -Technical (milder) ------------------- + 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. -* Tool renames. Give fixup patch for at least Cogito and StGIT. - [As of 2005-09-09 evening US/Pacific, the "master" branch has - what should go in 0.99.7 including gitenv() removal]. +* Maybe an Emacs VC backend. -* Have Daniel's read-tree graduate from "pu" after plugging leaks. +* 'git split-projects'? This requires updated 'git-rev-list' to + skip irrelevant commits. + Message-ID: -* Implement a merge backend using Daniel's read-tree [DONE]. +* Look at libified GNU diff CVS seems to use, or libxdiff. -* Rename 'git-merge-resolve' to 'git-merge-stupid' and - 'git-merge-multibase' to 'git-merge-resolve'; the former is - for historical curiosity and comparison purposes only and not - to be used in real applications so remove it from the default - strategies list [DONE]. -* Accept Fredrik merge after renaming it (I want to name the - driver 'git merge'). Suggest where to place *.py stuff -- - probably in $(share)/git-core/ and add Makefile entry for - installation. +Technical (milder) +------------------ * Encourage concrete proposals to commit log message templates we discussed some time ago. -* Bug Martin for archimport script documentation. - -* More portability. - * Accept patches to cause "read-tree -u" delete a directory when it makes it empty. @@ -152,24 +113,17 @@ Technical (milder) * Perhaps accept patch to optionally allow '--fuzz' in 'git-apply'. +* Allow 'git apply' to accept GNU diff 2.7 output that forgets + to say '\No newline' if both input ends with incomplete + lines. + * Maybe grok PGP signed text/plain in applymbox as well. * Perhaps a tool to revert a single file to pre-modification - state? git-cat-file blob `git-ls-files | grep foo` >foo or - git-cat-file blob `git-ls-tree HEAD foo` >foo? What should - the command be called? git-revert is taken so is - git-checkout. - -* A tool to detect, show and prune already merged topic - branches. - -* "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. - - Do not name it /lost+found/; that would probably confuse - things that mistake it a mount point (not our code but - somebody else's). + 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 @@ -181,11 +135,11 @@ Technical (milder) repository; experiment if this results in a reasonable workflow, and document it in howto form if it does. -* Option to limit rename detection for more than N paths. + 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 ;-). -* Marking copy seems to be broken when A,B => B,C rename - happens; we incorrectly say B stays, which makes the new B - copy of old A, not rename [DONE]. * Make rebase restartable; instead of skipping what cannot be automatically forward ported, leave the conflicts in the work @@ -194,21 +148,41 @@ Technical (milder) * Output full path in the "git-rev-list --objects" output, not just the basename, and see the improved clustering results in - better packing. + 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) ------------------- -* Teach 'git format-patch' about 'git cherry' [DONE]. +* 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]. + +* 'git merge-projects'? -* Make 'git bisect' easier to use by logging the earlier - good/bad choices and make it replayable [DONE]. + 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). -* Perhaps "git branch -d" to delete a branch. We probably need - some way to say "delete this branch because everything in this - should be merged in the master branch" and refuse the removal - if it is not true. +* 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