everyday: replace a few 'prune' and 'repack' with 'gc'
Signed-off-by: Junio C Hamano <junkio@cox.net>
Junio C Hamano committed
Dec 27, 2006 at 02:00 UTC
8f57b0a0fbfc0a6289bbf126f10ae041f0b508aa
1 file changed
+6
-3
Documentation/everyday.txt
+6
-3
@@ -34,6 +34,9 @@ Everybody uses these commands to maintain git repositories.
34
35
* gitlink:git-repack[1] to pack loose objects for efficiency.
36
37
+ * gitlink:git-gc[1] to do common housekeeping tasks such as
38
+ repack and prune.
39
+
40
Examples
41
~~~~~~~~
42
@@ -41,10 +44,9 @@ Check health and remove cruft.::
44
+
45
------------
46
$ git fsck-objects <1>
44
-$ git prune
47
$ git count-objects <2>
48
$ git repack <3>
47
-$ git prune <4>
49
+$ git gc <4>
50
------------
51
+
52
<1> running without `\--full` is usually cheap and assures the
@@ -53,7 +55,8 @@ repository health reasonably well.
55
disk space is wasted by not repacking.
56
<3> without `-a` repacks incrementally. repacking every 4-5MB
57
of loose objects accumulation may be a good rule of thumb.
56
-<4> after repack, prune removes the duplicate loose objects.
58
+<4> it is easier to use `git gc` than individual housekeeping commands
59
+such as `prune` and `repack`. This runs `repack -a -d`.
60
61
Repack a small project into single pack.::
62
+