git-prune(1) [suse man page]
GIT-PRUNE(1) Git Manual GIT-PRUNE(1) NAME
git-prune - Prune all unreachable objects from the object database SYNOPSIS
git prune [-n] [-v] [--expire <expire>] [--] [<head>...] DESCRIPTION
Note In most cases, users should run git gc, which calls git prune. See the section "NOTES", below. This runs git fsck --unreachable using all the refs available in refs/, optionally with additional set of objects specified on the command line, and prunes all unpacked objects unreachable from any of these head objects from the object database. In addition, it prunes the unpacked objects that are also found in packs by running git prune-packed. Note that unreachable, packed objects will remain. If this is not desired, see git-repack(1). OPTIONS
-n Do not remove anything; just report what it would remove. -v Report all removed objects. -- Do not interpret any more arguments as options. --expire <time> Only expire loose objects older than <time>. <head>... In addition to objects reachable from any of our references, keep objects reachable from listed <head>s. EXAMPLE
To prune objects not used by your repository nor another that borrows from your repository via its .git/objects/info/alternates: .ft C $ git prune $(cd ../another && $(git rev-parse --all)) .ft NOTES
In most cases, users will not need to call git prune directly, but should instead call git gc, which handles pruning along with many other housekeeping tasks. For a description of which objects are considered for pruning, see git fsck's --unreachable option. SEE ALSO
git-fsck(1), git-gc(1), git-reflog(1) AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]> DOCUMENTATION
Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org[2]>. GIT
Part of the git(1) suite NOTES
1. torvalds@osdl.org mailto:torvalds@osdl.org 2. git@vger.kernel.org mailto:git@vger.kernel.org Git 1.7.1 07/05/2010 GIT-PRUNE(1)
Check Out this Related Man Page
GIT-LOST-FOUND(1) Git Manual GIT-LOST-FOUND(1) NAME
git-lost-found - Recover lost refs that luckily have not yet been pruned SYNOPSIS
git lost-found DESCRIPTION
NOTE: this command is deprecated. Use git-fsck(1) with the option --lost-found instead. Finds dangling commits and tags from the object database, and creates refs to them in the .git/lost-found/ directory. Commits and tags that dereference to commits are stored in .git/lost-found/commit, and other objects are stored in .git/lost-found/other. OUTPUT
Prints to standard output the object names and one-line descriptions of any commits or tags found. EXAMPLE
Suppose you run git tag -f and mistype the tag to overwrite. The ref to your tag is overwritten, but until you run git prune, the tag itself is still there. .ft C $ git lost-found [1ef2b196d909eed523d4f3c9bf54b78cdd6843c6] GIT 0.99.9c ... .ft Also you can use gitk to browse how any tags found relate to each other. .ft C $ gitk $(cd .git/lost-found/commit && echo ??*) .ft After making sure you know which the object is the tag you are looking for, you can reconnect it to your regular .git/refs hierarchy. .ft C $ git cat-file -t 1ef2b196 tag $ git cat-file tag 1ef2b196 object fa41bbce8e38c67a218415de6cfa510c7e50032a type commit tag v0.99.9c tagger Junio C Hamano <junkio@cox.net> 1131059594 -0800 GIT 0.99.9c 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 1ef2b196d909eed523d4f3c9bf54b78cdd6843c6 .ft AUTHOR
Written by Junio C Hamano <gitster@pobox.com[1]> DOCUMENTATION
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org[2]>. GIT
Part of the git(1) suite NOTES
1. gitster@pobox.com mailto:gitster@pobox.com 2. git@vger.kernel.org mailto:git@vger.kernel.org Git 1.7.1 07/05/2010 GIT-LOST-FOUND(1)