Thread (1 message) 1 message, 1 author, 2016-06-15

Re: Seriously broken "git pack-refs"

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:51
Subsystem: documentation, the rest · Maintainers: Jonathan Corbet, Linus Torvalds

Possibly related (same subject, not in this thread)

Linus Torvalds [off-list ref] 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::
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help