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
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 ;-).
-Documentation
+Design issues
-------------
-* 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).
+* tree entries in index? -- sorry, stalled
-* Maybe update tutorial with a toy project that involves two or
- three developers..
+* "intent to add" index entries? -- together with the above
+ needs rethinking.
-* Update tutorial to cover setting up repository hooks to do
- common tasks.
-
-* 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)).
+* 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 (or kompare).
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 was already working on
+ this: <pan.2005.10.03.20.48.52.132570@smurf.noris.de>, but I
+ do not know what happened to his efforts]
-* Maybe a pack optimizer.
-
-* Maybe an Emacs VC backend.
-
-* 'git split-projects'? This requires updated 'git-rev-list' to
- skip irrelevant commits.
- Message-ID: <Pine.LNX.4.63.0509221617300.23242@iabervon.org>
-
-* Look at libified GNU diff CVS seems to use, or libxdiff.
+* Lazy clones that can be controlled by the user, ranging from
+ totally on-demand a la CVS/SVN to "cache down to this old
+ commit so that I can make full use of git on at least recent
+ history". This need a lot of work in making tools to exit
+ gracefully when they hit unavailable objects while offline.
Technical (milder)
------------------
-* Encourage concrete proposals to commit log message templates
- we discussed some time ago.
+* git grep should be able to omit prefix when invoked from a
+ subdirectory. Either make it an option or default with
+ --full-name like ls-files does.
-* Accept patches to cause "read-tree -u" delete a directory when
- it makes it empty.
+* duplicated refspec given to "fetch-pack a a a" makes it emit
+ strange error message because it triggers the "match only
+ once" logic. Maybe strip the dups on the input side
+ (Uwe Zeisberger
+ <20060608073857.GA5072@informatik.uni-freiburg.de>).
-* Perhaps accept patches to introduce the concept of "patch flow
- expressed as ref mappings" Josef has been advocating about.
+* map only parts of huge packfiles and LRU fragments of them.
+ People are starting to try git on projects with deep history
+ and/or many objects, e.g. Mozilla.
-* Perhaps accept patches to do undo/redo.
+* upload-pack support for start fetching from any valid point on
+ the history, not just published refs. (Erik W. Biederman
+ <m164jc9ekx.fsf@ebiederm.dsl.xmission.com>)
-* Perhaps accept patch to optionally allow '--fuzz' in
- 'git-apply'.
+* git-daemon side support for virtual hosting. Client side
+ is ready in 1.4.0 (Jon Loeliger <1149610100.23938.75.camel@cashmere.sps.mot.com>).
-* Allow 'git apply' to accept GNU diff 2.7 output that forgets
- to say '\No newline' if both input ends with incomplete
- lines.
+* teach git-upload-pack not to ack-continue early when the
+ client has roots it does not know about but it already has
+ learned the fork points for all the requested heads
+ (Ralf Baechle <20060524131022.GA11449@linux-mips.org>).
-* Maybe grok PGP signed text/plain in applymbox as well.
+* Per user .gitconfig across repositories -- ongoing.
-* 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.
+* Encourage competition between annotate vs blame. Maybe come
+ up with some nontrivial test cases.
-* Enhance "git repack" to not always use --all; this would be
- handy if the repository contains wagging heads like "pu" in
- git.git repository.
+* Subprojects. Try "gitlink" -- sorry, stalled.
-* 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.
+* Rebase and checkout -m should be able to use recursive
+ strategy as well. These commands currently do not work across
+ renames.
-* 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.
+* 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.
-* 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].
+ <43CC695E.2020506@codeweavers.com>
-* 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].
+* 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 this does not feel quite right.
+ <20060114021800.4688.qmail@web31803.mail.mud.yahoo.com>
-Technical (trivial)
--------------------
+* 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.
-* short SHA1 naming is not enforcing uniqueness. Should fix.
+* daemon --strict-symlink.
-* 'git repack' can be DOSed. Should fix.
+* daemon --base-path does not apply automatically to whitelist
+ somehow feels wrong. If somebody cares enough, accept
+ patches.
-* Stop installing the old-name symlinks [POSTPONED].
+* Perhaps detect cloning request in upload-pack and cache the
+ result for next cloning request until any of our refs change.
-* 'git merge-projects'?
+* Maybe grok PGP signed text/plain in applymbox as well.
-* '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).
+Technical (trivial)
+-------------------
-* 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/).
+* git-proxy should be spawned with sh -c 'command' $1 $2.
-* 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:
+* Maybe a true git-proxy command that reads the first request
+ pkt-line, and redirects the request to its real destination.
- 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`).