Re: [PATCH v2] gc: call "prune --expire 2.weeks.ago" by default

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 12, 2008, 19:07 UTC
Message-ID: <alpine.LSU.1.00.0803122005330.1656@racer.site>
In-Reply-To: <m3prtzyens.fsf@localhost.localdomain>

Hi,

On Wed, 12 Mar 2008, Jakub Narebski wrote:

Show 8 quoted lines

> Brandon Casey <casey@nrlssc.navy.mil> writes:
> 
> > Is 'git-gc --prune' still useful to end users when those in-the-know 
> > can use git-prune when they really want all loose unreferenced objects 
> > to be removed?
> 
> It is one command less to remember (just like with "git tag --verify" 
> and "git verify-tag"), so I'm all for "git gc --prune" to remain.

I don't care one way or the other.

> > Also, what about clones created with --shared or --reference? Should 
> > there be a way to disable this functionality? gc.pruneExpire never
> 
> That would be nice.

Okay, so I just remove the !approxidate() check. Then, "gc.pruneExpire = never" should work as you expect it to.

Ciao, Dscho