-* 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.
-
-* 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.
-
-* 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].
-
-* Remove obsolete commands [DONE].
-
-* Option to limit rename detection for more than N paths [DONE].
-
-* Option to show only status and name from diff [DONE].
-
-* What to name the 'master' version between 0.99.7 and 0.99.8
- and still not break binary distribution folks? 0.99.7z?
- Pasky gave me a good one: 0.99.7.GIT [DONE]
-
-* Listing more than one head on the Pull: line of .git/remotes/
- allows you to make Octopus -- is it useful? Probabaly not.
- Either adopt "only the first head is used for the merge by
- default if taken from .git/remotes/ file", or "list heads to
- merge on a separate Merge: line" proposal. I already have the
- code to do the former, so...
-