6 git-lost-found - Recover lost refs that luckily have not yet been pruned
15 *NOTE*: this command is deprecated. Use linkgit:git-fsck[1] with
16 the option '--lost-found' instead.
18 Finds dangling commits and tags from the object database, and
19 creates refs to them in the .git/lost-found/ directory. Commits and
20 tags that dereference to commits are stored in .git/lost-found/commit,
21 and other objects are stored in .git/lost-found/other.
26 Prints to standard output the object names and one-line descriptions
27 of any commits or tags found.
32 Suppose you run 'git tag -f' and mistype the tag to overwrite.
33 The ref to your tag is overwritten, but until you run 'git
34 prune', the tag itself is still there.
38 [1ef2b196d909eed523d4f3c9bf54b78cdd6843c6] GIT 0.99.9c
42 Also you can use gitk to browse how any tags found relate to each
46 $ gitk $(cd .git/lost-found/commit && echo ??*)
49 After making sure you know which the object is the tag you are looking
50 for, you can reconnect it to your regular .git/refs hierarchy.
53 $ git cat-file -t 1ef2b196
55 $ git cat-file tag 1ef2b196
56 object fa41bbce8e38c67a218415de6cfa510c7e50032a
59 tagger Junio C Hamano <junkio@cox.net> 1131059594 -0800
63 This contains the following changes from the "master" branch, since
65 $ git update-ref refs/tags/not-lost-anymore 1ef2b196
66 $ git rev-parse not-lost-anymore
67 1ef2b196d909eed523d4f3c9bf54b78cdd6843c6
72 Written by Junio C Hamano <gitster@pobox.com>
76 Documentation by Junio C Hamano and the git-list <git@vger.kernel.org>.
81 Part of the linkgit:git[1] suite