Document gc.<pattern>.reflogexpire variables
3cb22b8 (Per-ref reflog expiry configuration, 2008-06-15) added support for setting the expiry parameters differently for different reflog, but it was never documented. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Apr 14, 2010 at 13:12 UTC
eb523a8d795e31e84cc8af5c43b913ed0cd073b1
2 files changed
+18
-2
Documentation/config.txt
+8
-2
@@ -885,13 +885,19 @@ gc.pruneexpire::
885
unreachable objects immediately.
886
887
gc.reflogexpire::
888
+gc.<pattern>.reflogexpire::
889
'git-reflog expire' removes reflog entries older than
889
- this time; defaults to 90 days.
890
+ this time; defaults to 90 days. With "<pattern>" (e.g.
891
+ "refs/stash") in the middle the setting applies only to
892
+ the refs that match the <pattern>.
893
894
gc.reflogexpireunreachable::
895
+gc.<ref>.reflogexpireunreachable::
896
'git-reflog expire' removes reflog entries older than
897
this time and are not reachable from the current tip;
894
- defaults to 30 days.
898
+ defaults to 30 days. With "<pattern>" (e.g. "refs/stash")
899
+ in the middle, the setting applies only to the refs that
900
+ match the <pattern>.
901
902
gc.rerereresolved::
903
Records of conflicted merge you resolved earlier are
Documentation/git-gc.txt
+10
@@ -88,6 +88,16 @@ commits prior to the amend or rebase occurring. Since these changes
88
are not part of the current project most users will want to expire
89
them sooner. This option defaults to '30 days'.
90
91
+The above two configuration variables can be given to a pattern. For
92
+example, this sets non-default expiry values only to remote tracking
93
+branches:
94
+
95
+------------
96
+[gc "refs/remotes/*"]
97
+ reflogExpire = never
98
+ reflogexpireUnreachable = 3 days
99
+------------
100
+
101
The optional configuration variable 'gc.rerereresolved' indicates
102
how long records of conflicted merge you resolved earlier are
103
kept. This defaults to 60 days.