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
-------------
+* 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.
* 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: <pan.2005.10.03.20.48.52.132570@smurf.noris.de>; Post
+ 1.0].
* Maybe a pack optimizer.
+ 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.
+
* Maybe an Emacs VC backend.
* 'git split-projects'? This requires updated 'git-rev-list' to
Message-ID: <Pine.LNX.4.63.0509221617300.23242@iabervon.org>
* 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.
Technical (milder)
------------------
+* Funny tag names and curl library.
+
+ curl 'http://locke.catalyst.net.nz/git/moodle.git/refs/tags/MOODLE_15_MERGED **INVALID**'
+
+* Review the Makefile variables and exporting rules for them,
+ while looking at prefix passing by Kai Ruemmler [DONE].
+
+* Review the 'sparce object database' change by Linus and move
+ the first phase of it to the "master" branch [DONE].
+
+* 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].
+
+* Revisit Santi's patch to move commit temorary files out of the
+ working tree toplevel [DONE].
+
+* 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.
+
+* Perhaps accept more "want"s in upload-pack and do something
+ intelligent about it.
+
+* Perhaps detect cloning request in upload-pack and cache the
+ result for next cloning request until any of our refs change.
+
+* Perhaps send less "want"s from fetch-pack.
+
* Encourage concrete proposals to commit log message templates
we discussed some time ago.
* Accept patches to cause "read-tree -u" delete a directory when
it makes it empty.
-* Perhaps accept patches to introduce the concept of "patch flow
- expressed as ref mappings" Josef has been advocating about.
-
* Perhaps accept patches to do undo/redo.
* Perhaps accept patch to optionally allow '--fuzz' in
to say '\No newline' if both input ends with incomplete
lines.
+* What to do with TABs and LFs in pathnames without breaking GNU
+ patch? [Discussion started.]
+
* Maybe grok PGP signed text/plain in applymbox as well.
* Perhaps a tool to revert a single file to pre-modification
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
external spec sent out with a quick hack. Will know if that
is what he needs soon enough].
+* An mechanism to ignore filesystem mode bits altogether.
+
Technical (trivial)
-------------------
-* short SHA1 naming is not enforcing uniqueness. Should fix.
+* short SHA1 naming is not enforcing uniqueness. Should fix [DONE].
-* 'git repack' can be DOSed. Should fix.
+* 'git repack' can be DOSed. Should fix [DONE].
-* Stop installing the old-name symlinks [POSTPONED].
+* 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
projects / git.git / blobdiff