From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: [PATCH] Add commands that git-gc runs underneath
Date: Thu, 30 Aug 2007 12:35:11 +0300 [thread overview]
Message-ID: <lkbtwek0.fsf@cante.net> (raw)
git-gc is a higher level utility to "do the right thing". However
there are many other lower level utilities for the house keeping and
it is not clear what git-gc actually does. Adding the actual lower
level command and their parameters explain "what's going on".x
Signed-off-by: Jari Aalto <jari.aalto@cante.net>
---
Documentation/git-gc.txt | 18 ++++++++++++++++++
1 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-gc.txt b/Documentation/git-gc.txt
index c7742ca..c2315bf 100644
--- a/Documentation/git-gc.txt
+++ b/Documentation/git-gc.txt
@@ -21,6 +21,24 @@ Users are encouraged to run this task on a regular basis within
each repository to maintain good disk space utilization and good
operating performance.
+`git-gc` is a front-end to lower level house keeping commands and
+effectively runs these:
+
+--------------------------------
+ # for non-bare repositories only
+ git pack-refs --all --prune
+
+ git reflog expire --all
+
+ # with added --window -f parameters if --aggressive was specified
+ git repack -a -d -l
+
+ # if --prune was specified
+ git prune
+
+ git rerere gc
+--------------------------------
+
OPTIONS
-------
--
1.5.3.rc5
--
Welcome to FOSS revolution: we fix and modify until it shines
next reply other threads:[~2007-08-30 9:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 9:35 Jari Aalto [this message]
2007-08-30 10:08 ` [PATCH] Add commands that git-gc runs underneath Johannes Schindelin
2007-08-30 10:13 ` Andreas Ericsson
2007-08-30 11:58 ` Johannes Schindelin
2007-08-30 12:13 ` Andreas Ericsson
2007-08-30 12:15 ` Tom Clarke
2007-08-30 12:34 ` Theodore Tso
2007-08-30 21:33 ` Junio C Hamano
2007-08-31 9:33 ` Andreas Ericsson
2007-08-31 19:25 ` David Kastrup
2007-08-31 21:12 ` Junio C Hamano
2007-08-31 21:27 ` David Kastrup
2007-08-30 10:25 ` David Kastrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lkbtwek0.fsf@cante.net \
--to=jari.aalto@cante.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox