aboutsummaryrefslogtreecommitdiff
path: root/Documentation/everyday.txt
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2006-12-27 16:43:15 -0800
committerJunio C Hamano <junkio@cox.net>2006-12-27 16:43:15 -0800
commit7c20b8234af2962ea4d5ce930ec0308c33f6f654 (patch)
tree908fc0e9d0f2dac92ba64a84427c53560afdecd1 /Documentation/everyday.txt
parent87ac1390d9ac2ab5e495b543caee12221a773fb7 (diff)
parenta3c11db9ecf5c2a1ec1b25ba809cecb3747750d4 (diff)
downloadgit-7c20b8234af2962ea4d5ce930ec0308c33f6f654.tar.gz
git-7c20b8234af2962ea4d5ce930ec0308c33f6f654.tar.xz
Merge branch 'sp/gc'
* sp/gc: Use 'repack -a -d -l' instead of 'repack -a -d' in git-gc everyday: replace a few 'prune' and 'repack' with 'gc' Create 'git gc' to perform common maintenance operations.
Diffstat (limited to 'Documentation/everyday.txt')
-rw-r--r--Documentation/everyday.txt9
1 files changed, 6 insertions, 3 deletions
diff --git a/Documentation/everyday.txt b/Documentation/everyday.txt
index 5d17ace72..2105a3d2e 100644
--- a/Documentation/everyday.txt
+++ b/Documentation/everyday.txt
@@ -34,6 +34,9 @@ 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
~~~~~~~~
@@ -41,10 +44,9 @@ 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
@@ -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.::
+