48bb914ed6
The point of these sections is generally to:
1. Give credit where it is due.
2. Give the reader an idea of where to ask questions or
file bug reports.
But they don't do a good job of either case. For (1), they
are out of date and incomplete. A much more accurate answer
can be gotten through shortlog or blame. For (2), the
correct contact point is generally git@vger, and even if you
wanted to cc the contact point, the out-of-date and
incomplete fields mean you're likely sending to somebody
useless.
So let's drop the fields entirely from all manpages except
git(1) itself. We already point people to the mailing list
for bug reports there, and we can update the Authors section
to give credit to the major contributors and point to
shortlog and blame for more information.
Each page has a "This is part of git" footer, so people can
follow that to the main git manpage.
84 lines
1.8 KiB
Plaintext
84 lines
1.8 KiB
Plaintext
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 linkgit:git-repack[1].
|
|
|
|
OPTIONS
|
|
-------
|
|
|
|
-n::
|
|
--dry-run::
|
|
Do not remove anything; just report what it would
|
|
remove.
|
|
|
|
-v::
|
|
--verbose::
|
|
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`:
|
|
|
|
------------
|
|
$ git prune $(cd ../another && $(git rev-parse --all))
|
|
------------
|
|
|
|
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
|
|
--------
|
|
|
|
linkgit:git-fsck[1],
|
|
linkgit:git-gc[1],
|
|
linkgit:git-reflog[1]
|
|
|
|
GIT
|
|
---
|
|
Part of the linkgit:git[1] suite
|