+* Disallow [\001-\040\177] byte values from ref names. Also we
+ need to disallow ':' (used in refspec), '^' and '~' (postfix
+ "peel the onion" operators), and '..' ("ref1..ref2" notation
+ becomes ambiguous otherwise) [DONE].
+
+* Update fetch-pack and clone-pack to ignore funny refs from the
+ other end, while making sure peek-remote does not discard them.
+ [DONE]
+
+* Update upload-pack to send tag^{}. This would hopefully help
+ Pasky's automated tag tracking, and also Martin's findtags.
+ [DONE]
+
+* Adjust update-index to quoted --index-info [DONE].
+
+* Prepare apply.c changes for maint branch (0.99.8e) [DONE].
+
+* Perhaps show ^{commit}, ^{tree} instead of ^{} from ls-remote? [NO]
+
+* Re-adjust maint branch for the above if we did so. [NOT NEEDED]
+
+* short SHA1 naming is not enforcing uniqueness. Should fix [DONE].
+
+* 'git repack' can be DOSed. Should fix [DONE].
+
+* Stop installing the old-name symlinks [IN 0.99.9].
+
+* '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
+ 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).