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