Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.16.1 → 2.17.0 no changes
- 2.16.0 01/17/18
|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
$GIT_DIR/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
Note that unreachable, packed objects will remain. If this is not desired, see git-repack.
Do not remove anything; just report what it would remove.
Report all removed objects.
Do not interpret any more arguments as options.
- --expire <time>
Only expire loose objects older than <time>.
In addition to objects reachable from any of our references, keep objects reachable from listed <head>s.
To prune objects not used by your repository nor another that
borrows from your repository via its
$ git prune $(cd ../another && $(git rev-parse --all))
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.
Written by Linus Torvalds <firstname.lastname@example.org>
Documentation by David Greaves, Junio C Hamano and the git-list <email@example.com>.
Part of the git suite