From: Junio C Hamano <junkio@cox•net>
To: Linus Torvalds <torvalds@linux-foundation•org>
Cc: git@vger•kernel.org
Subject: Re: Seriously broken "git pack-refs"
Date: Thu, 25 Jan 2007 22:50:18 -0800 [thread overview]
Message-ID: <7vac062set.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0701252218540.25027@woody.linux-foundation.org> (Linus Torvalds's message of "Thu, 25 Jan 2007 22:24:35 -0800 (PST)")
Linus Torvalds <torvalds@linux-foundation•org> writes:
> Tags automatically fall under that heading (which is why it makes sense to
> pack them by default in the first place!) but so does any ref that was
> already packed, and hadn't become unpacked since the last repack. By
> definition, such a ref isn't "actively changing" even if it isn't a tag.
>
> No?
Yes.
diff --git a/Documentation/git-pack-refs.txt b/Documentation/git-pack-refs.txt
index 464269f..b79b79d 100644
--- a/Documentation/git-pack-refs.txt
+++ b/Documentation/git-pack-refs.txt
@@ -34,11 +34,16 @@ OPTIONS
\--all::
-The command by default packs all tags and leaves branch tips
+The command by default packs all tags and refs that are already
+packed, and leaves other refs
alone. This is because branches are expected to be actively
developed and packing their tips does not help performance.
This option causes branch tips to be packed as well. Useful for
a repository with many branches of historical interests.
+Once packing with `\--all` is done, further repacking with the
+default will keep the already packed refs (including branch
+heads) packed, while still actively developed branch heads will
+not be packed (because they become unpacked once modified).
\--no-prune::
prev parent reply other threads:[~2007-01-26 6:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 0:51 Seriously broken "git pack-refs" Linus Torvalds
2007-01-26 3:22 ` Junio C Hamano
2007-01-26 6:05 ` Linus Torvalds
2007-01-26 6:08 ` Junio C Hamano
2007-01-26 6:24 ` Linus Torvalds
2007-01-26 6:50 ` Junio C Hamano [this message]
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=7vac062set.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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