+git-lost+found - Recover lost refs that luckily have not yet been pruned.
+Finds dangling commits and tags from the object database, and
+creates refs to them in .git/lost+found/ directory. Commits and
+tags that dereference to commits go to .git/lost+found/commit
+and others are stored in .git/lost+found/other directory.
+One line description from the commit and tag found along with
+their object name are printed on the standard output.
+Suppose you run 'git tag -f' and mistyped the tag to overwrite.
+The ref to your tag is overwritten, but until you run 'git
+prune', it is still there.
+[1ef2b196d909eed523d4f3c9bf54b78cdd6843c6] GIT 0.99.9c
+Also you can use gitk to browse how they relate to each other
+and existing (probably old) tags.
+$ gitk $(cd .git/lost+found/commit && echo ??*)
+After making sure that it is the object you are looking for, you
+can reconnect it to your regular .git/refs hierarchy.
+$ git cat-file -t 1ef2b196
+$ git cat-file tag 1ef2b196
+tagger Junio C Hamano <firstname.lastname@example.org> 1131059594 -0800
+This contains the following changes from the "master" branch, since
+$ git update-ref refs/tags/not-lost-anymore 1ef2b196
+$ git rev-parse not-lost-anymore
+Written by Junio C Hamano <email@example.com>
+Documentation by Junio C Hamano and the git-list <firstname.lastname@example.org>.
+Part of the gitlink:git suite