From: Brandon Casey <casey@nrlssc.navy.mil>
Date: Wed, 12 Mar 2008 17:56:11 GMT
Subject: Re: [PATCH v2] gc: call "prune --expire 2.weeks.ago" by default
Message-ID: <47D8193B.901@nrlssc.navy.mil>
In-Reply-To: <alpine.LSU.1.00.0803121833210.1656@racer.site>

Johannes Schindelin wrote:
> If you want to override this grace period, just set the config variable
> gc.pruneExpire to a different value; an example would be
> 
> 	[gc]
> 		pruneExpire = 6.months.ago
> 
> if you feel really paranoid.
> 
> Note that this new behaviour does not affect git-gc when you pass the
> option --prune; in that case, prune will clean up the loose objects with no
> grace period at all.

Hmm. Perhaps 'git-gc' should always call 'prune' with the '--expire' argument
for simplicity of the 'git-gc' interface and --prune should become a noop?

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?

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

-brandon