This document is for newcomers, so it's good to mention gc for housekeeping tasks instead of running prune manually. Signed-off-by: Miklos Vajna <vmiklos@xxxxxxxxxxxxxx> --- Documentation/everyday.txt | 8 +++----- 1 files changed, 3 insertions(+), 5 deletions(-) diff --git a/Documentation/everyday.txt b/Documentation/everyday.txt index ce7c170..a09c1d9 100644 --- a/Documentation/everyday.txt +++ b/Documentation/everyday.txt @@ -30,8 +30,6 @@ Everybody uses these commands to maintain git repositories. * gitlink:git-fsck[1] to check the repository for errors. - * gitlink:git-prune[1] to remove unused objects in the repository. - * gitlink:git-repack[1] to pack loose objects for efficiency. * gitlink:git-gc[1] to do common housekeeping tasks such as @@ -56,13 +54,13 @@ 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> it is easier to use `git gc` than individual housekeeping commands -such as `prune` and `repack`. This runs `repack -a -d`. +such as `prune` and `repack`. Repack a small project into single pack.:: + ------------ $ git repack -a -d <1> -$ git prune +$ git gc --prune ------------ + <1> pack all the objects reachable from the refs into one pack, @@ -189,7 +187,7 @@ $ git pull <3> $ git log -p ORIG_HEAD.. arch/i386 include/asm-i386 <4> $ git pull git://git.kernel.org/pub/.../jgarzik/libata-dev.git ALL <5> $ git reset --hard ORIG_HEAD <6> -$ git prune <7> +$ git gc --prune <7> $ git fetch --tags <8> ------------ + -- 1.5.4.rc0.67.gf9c5-dirty - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
