1git-lost-found(1) 2================= 3 4NAME 5---- 6git-lost-found - Recover lost refs that luckily have not yet been pruned 7 8SYNOPSIS 9-------- 10[verse] 11'git lost-found' 12 13DESCRIPTION 14----------- 15 16*NOTE*: this command is deprecated. Use linkgit:git-fsck[1] with 17the option '--lost-found' instead. 18 19Finds dangling commits and tags from the object database, and 20creates refs to them in the .git/lost-found/ directory. Commits and 21tags that dereference to commits are stored in .git/lost-found/commit, 22and other objects are stored in .git/lost-found/other. 23 24 25OUTPUT 26------ 27Prints to standard output the object names and one-line descriptions 28of any commits or tags found. 29 30EXAMPLE 31------- 32 33Suppose you run 'git tag -f' and mistype the tag to overwrite. 34The ref to your tag is overwritten, but until you run 'git 35prune', the tag itself is still there. 36 37------------ 38$ git lost-found 39[1ef2b196d909eed523d4f3c9bf54b78cdd6843c6] GIT 0.99.9c 40... 41------------ 42 43Also you can use gitk to browse how any tags found relate to each 44other. 45 46------------ 47$ gitk $(cd .git/lost-found/commit && echo ??*) 48------------ 49 50After making sure you know which the object is the tag you are looking 51for, you can reconnect it to your regular .git/refs hierarchy. 52 53------------ 54$ git cat-file -t 1ef2b196 55tag 56$ git cat-file tag 1ef2b196 57object fa41bbce8e38c67a218415de6cfa510c7e50032a 58type commit 59tag v0.99.9c 60tagger Junio C Hamano <junkio@cox.net> 1131059594 -0800 61 62GIT 0.99.9c 63 64This contains the following changes from the "master" branch, since 65... 66$ git update-ref refs/tags/not-lost-anymore 1ef2b196 67$ git rev-parse not-lost-anymore 681ef2b196d909eed523d4f3c9bf54b78cdd6843c6 69------------ 70 71GIT 72--- 73Part of the linkgit:git[1] suite