gc docs: stop noting "repack" flags
Remove the mention of specific flags from the "gc" documentation, and leave it at describing what we'll do instead. As seen in builtin/gc.c we'll use various repack flags depending on what we detect we need to do, so this isn't always accurate. More importantly, a subsequent change is about to remove all this documentation and replace it with an include of the gc.* docs in git-config(1). By first changing this it's easier to reason about that subsequent change. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Ævar Arnfjörð Bjarmason committed
Mar 22, 2019 at 10:32 UTC
cf9cd771e1314ad5cd8eaf1d92b7a5fd5e6b734f
1 file changed
+2
-3
Documentation/git-gc.txt
+2
-3
@@ -52,14 +52,13 @@ OPTIONS
52
+
53
If the number of loose objects exceeds the value of the `gc.auto`
54
configuration variable, then all loose objects are combined into a
55
-single pack using `git repack -d -l`. Setting the value of `gc.auto`
55
+single pack. Setting the value of `gc.auto`
56
to 0 disables automatic packing of loose objects.
57
+
58
If the number of packs exceeds the value of `gc.autoPackLimit`,
59
then existing packs (except those marked with a `.keep` file
60
or over `gc.bigPackThreshold` limit)
61
-are consolidated into a single pack by using the `-A` option of
62
-'git repack'.
61
+are consolidated into a single pack.
62
If the amount of memory is estimated not enough for `git repack` to
63
run smoothly and `gc.bigPackThreshold` is not set, the largest
64
pack will also be excluded (this is the equivalent of running `git gc`