From: Shawn Pearce <spearce@spearce.org>
Date: Wed, 27 Dec 2006 07:53:30 GMT
Subject: Re: [PATCH] Create 'git gc' to perform common maintenance operations.
Message-ID: <20061227075330.GA23022@spearce.org>
In-Reply-To: <7vr6ul93wz.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <junkio@cox.net> wrote:
> "Shawn O. Pearce" <spearce@spearce.org> writes:
> 
> > +The optional configuration variable 'gc.reflogExpireUnreachable'
> > +can be set to indicate how long historical reflog entries which
> > +are not part of the current branch should remain available in
> > +this repository.  These types of entries are generally created as
> > +a result of using `git commit \--amend` or `git rebase` and are the
> > +commits prior to the amend or rebase occuring.  Since these changes
> > +are not part of the current project most users will want to expire
> > +them sooner.  This option defaults to '60 days'.
> 
> Should I update the default expire-unreachable in builtin-reflog
> to match 60 days?

Doh, I meant for git-gc to match the default in 'git-reflog expire'.
Whoops.

I don't care either way.  60 days may be too long for some users,
but for others it may be nice to have.  I think the two defaults
should match just because.  Feel free to edit my patch before
applying to be whatever 'git-reflog expire' uses if you want.

-- 
Shawn.