summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: 30f610b)
raw | patch | inline | side by side (parent: 30f610b)
author | Junio C Hamano <junkio@cox.net> | |
Wed, 27 Dec 2006 10:00:30 +0000 (02:00 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Wed, 27 Dec 2006 10:00:30 +0000 (02:00 -0800) |
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/everyday.txt | patch | blob | history |
index 5d17ace721d1ec4c031a4a1f96374559002a93c9..2105a3d2e7337105263c8a9fef466609c63fc163 100644 (file)
* 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
~~~~~~~~
+
------------
$ 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
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.::
+