gc docs: re-flow the "gc.*" section in "config"
Re-flow the "gc.*" section in "config". A previous commit moved this over from the "gc" docs, but tried to keep as many of the lines identical to benefit from diff's move detection. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Ævar Arnfjörð Bjarmason committed
Apr 7, 2019 at 21:52 UTC
d257e0fb0adc1eefa8e237391cd0e3aaa9d69e9d
1 file changed
+8
-9
Documentation/config/gc.txt
+8
-9
@@ -53,9 +53,9 @@ will be repacked. After this the number of packs should go below
53
gc.autoPackLimit and gc.bigPackThreshold should be respected again.
54
+
55
If the amount of memory estimated for `git repack` to run smoothly is
56
-not available and `gc.bigPackThreshold` is not set, the largest
57
-pack will also be excluded (this is the equivalent of running `git gc`
58
-with `--keep-base-pack`).
56
+not available and `gc.bigPackThreshold` is not set, the largest pack
57
+will also be excluded (this is the equivalent of running `git gc` with
58
+`--keep-base-pack`).
59
60
gc.writeCommitGraph::
61
If true, then gc will rewrite the commit-graph file when
@@ -115,12 +115,11 @@ gc.<pattern>.reflogExpireUnreachable::
115
in the middle, the setting applies only to the refs that
116
match the <pattern>.
117
+
118
-These types of entries are generally created as
119
-a result of using `git commit --amend` or `git rebase` and are the
120
-commits prior to the amend or rebase occurring. Since these changes
121
-are not part of the current project most users will want to expire
122
-them sooner, which is why the default is more aggressive than
123
-`gc.reflogExpire`.
118
+These types of entries are generally created as a result of using `git
119
+commit --amend` or `git rebase` and are the commits prior to the amend
120
+or rebase occurring. Since these changes are not part of the current
121
+project most users will want to expire them sooner, which is why the
122
+default is more aggressive than `gc.reflogExpire`.
123
124
gc.rerereResolved::
125
Records of conflicted merge you resolved earlier are