6 git-lost-found - Recover lost refs that luckily have not yet been pruned
16 *NOTE*: this command is deprecated. Use linkgit:git-fsck[1] with
17 the option '--lost-found' instead.
19 Finds dangling commits and tags from the object database, and
20 creates refs to them in the .git/lost-found/ directory. Commits and
21 tags that dereference to commits are stored in .git/lost-found/commit,
22 and other objects are stored in .git/lost-found/other.
27 Prints to standard output the object names and one-line descriptions
28 of any commits or tags found.
33 Suppose you run 'git tag -f' and mistype the tag to overwrite.
34 The ref to your tag is overwritten, but until you run 'git
35 prune', the tag itself is still there.
39 [1ef2b196d909eed523d4f3c9bf54b78cdd6843c6] GIT 0.99.9c
43 Also you can use gitk to browse how any tags found relate to each
47 $ gitk $(cd .git/lost-found/commit && echo ??*)
50 After making sure you know which the object is the tag you are looking
51 for, you can reconnect it to your regular .git/refs hierarchy.
54 $ git cat-file -t 1ef2b196
56 $ git cat-file tag 1ef2b196
57 object fa41bbce8e38c67a218415de6cfa510c7e50032a
60 tagger Junio C Hamano <junkio@cox.net> 1131059594 -0800
64 This contains the following changes from the "master" branch, since
66 $ git update-ref refs/tags/not-lost-anymore 1ef2b196
67 $ git rev-parse not-lost-anymore
68 1ef2b196d909eed523d4f3c9bf54b78cdd6843c6
73 Part of the linkgit:git[1] suite