Skip to content

Commit

Permalink
everyday: replace a few 'prune' and 'repack' with 'gc'
Browse files Browse the repository at this point in the history
Signed-off-by: Junio C Hamano <junkio@cox.net>
  • Loading branch information
Junio C Hamano committed Dec 27, 2006
1 parent 30f610b commit 8f57b0a
Showing 1 changed file with 6 additions and 3 deletions.
9 changes: 6 additions & 3 deletions Documentation/everyday.txt
Original file line number Diff line number Diff line change
Expand Up @@ -34,17 +34,19 @@ Everybody uses these commands to maintain git repositories.

* gitlink:git-repack[1] to pack loose objects for efficiency.

* gitlink:git-gc[1] to do common housekeeping tasks such as
repack and prune.

Examples
~~~~~~~~

Check health and remove cruft.::
+
------------
$ git fsck-objects <1>
$ git prune
$ git count-objects <2>
$ git repack <3>
$ git prune <4>
$ git gc <4>
------------
+
<1> running without `\--full` is usually cheap and assures the
Expand All @@ -53,7 +55,8 @@ repository health reasonably well.
disk space is wasted by not repacking.
<3> without `-a` repacks incrementally. repacking every 4-5MB
of loose objects accumulation may be a good rule of thumb.
<4> after repack, prune removes the duplicate loose objects.
<4> it is easier to use `git gc` than individual housekeeping commands
such as `prune` and `repack`. This runs `repack -a -d`.

Repack a small project into single pack.::
+
Expand Down

0 comments on commit 8f57b0a

Please sign in to comment.