From: Florian La Roche <laroche@redhat.com>
To: git@vger.kernel.org, gitster@pobox.com
Subject: [PATCH] Change git-gc documentation to reflect gc.packrefs implementation.
Date: Wed, 9 Jan 2008 17:05:16 +0100 [thread overview]
Message-ID: <20080109160516.GA31535@dudweiler.stuttgart.redhat.com> (raw)
Adjust git-gc documentation to reflect gc.packrefs implementation.
Adjust git-gc documentation to reflect gc.packrefs implementation.
Signed-off-by: Florian La Roche <laroche@redhat.com>
---
Documentation/git-gc.txt | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-gc.txt b/Documentation/git-gc.txt
index c4354bb..4b2dfef 100644
--- a/Documentation/git-gc.txt
+++ b/Documentation/git-gc.txt
@@ -90,9 +90,9 @@ how long records of conflicted merge you have not resolved are
kept. This defaults to 15 days.
The optional configuration variable 'gc.packrefs' determines if
-`git gc` runs `git-pack-refs`. Without the configuration, `git-pack-refs`
-is not run in bare repositories by default, to allow older dumb-transport
-clients fetch from the repository, but this will change in the future.
+`git gc` runs `git-pack-refs`. This can be set to "nobare" to enable
+it within all non-bare repos or it can be set to a boolean value.
+This defaults to true.
The optional configuration variable 'gc.aggressiveWindow' controls how
much time is spent optimizing the delta compression of the objects in
--
1.5.3.7
next reply other threads:[~2008-01-09 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 16:05 Florian La Roche [this message]
2008-01-09 20:25 ` [PATCH] Change git-gc documentation to reflect gc.packrefs implementation Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2008-01-07 16:21 Florian La Roche
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=20080109160516.GA31535@dudweiler.stuttgart.redhat.com \
--to=laroche@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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;
as well as URLs for NNTP newsgroup(s).