-* 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.
-
-* "git cherry-pick" that applies the patch an existing commit
- introduces in its ancestry chain, possibly using the 3-way
- merge machinery. [DONE]
-
-* Update rebase using the cherry-pick command. [DONE]
-
-* Redo "git revert" using 3-way merge machinery. [DONE]
-
-* A tool to detect, show and prune already merged topic
- branches.
-
-* Set up an automated documentation rebuilding procedure at
- kernel.org, using update hook mechanism. [DONE]
-
-* Describe automated documentation rebuilding in a howto form
- [DONE].
-
-* Enhance "git repack" to not always use --all; this would be
- handy if the repository contains wagging heads like "pu" in
- git.git repository.
-
-* Accept and apply "git repack --all" patch, except the part
- that removes the existing packs. [DONE]
-
-* 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.
-
-* Add names to all nodes in show-branch [DONE].
-
-* Option to limit rename detection for more than N paths.
-