From eb523a8d795e31e84cc8af5c43b913ed0cd073b1 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Wed, 14 Apr 2010 13:12:34 -0700 Subject: Document gc..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 --- Documentation/git-gc.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'Documentation/git-gc.txt') diff --git a/Documentation/git-gc.txt b/Documentation/git-gc.txt index 4cd9cdf905..85d7111929 100644 --- a/Documentation/git-gc.txt +++ b/Documentation/git-gc.txt @@ -88,6 +88,16 @@ commits prior to the amend or rebase occurring. Since these changes are not part of the current project most users will want to expire them sooner. This option defaults to '30 days'. +The above two configuration variables can be given to a pattern. For +example, this sets non-default expiry values only to remote tracking +branches: + +------------ +[gc "refs/remotes/*"] + reflogExpire = never + reflogexpireUnreachable = 3 days +------------ + The optional configuration variable 'gc.rerereresolved' indicates how long records of conflicted merge you resolved earlier are kept. This defaults to 60 days. -- cgit v1.2.1