From: Jeff King <peff@peff.net>
Date: Sun, 14 Dec 2008 11:19:39 GMT
Subject: Re: [PATCH] bash completion: remove deprecated --prune from git-gc
Message-ID: <20081214111939.GC6499@coredump.intra.peff.net>
In-Reply-To: <alpine.DEB.1.00.0812141216120.2014@eeepc-johanness>

On Sun, Dec 14, 2008 at 12:17:07PM +0100, Johannes Schindelin wrote:

> > Which annoyingly has no discussion about _why_ it no longer has an
> > effect. But I suspect it has something to do with 25ee973 (gc: call
> > "prune --expire 2.weeks.ago" by default, 2008-03-12) by you.
> 
> Oops.
> 
> But I thought that git gc --prune does expire _all_ dangling loose 
> objects _now_, not with --expire 2.weeks.ago.

Nope, see 25ee973. You explicitly wrote:

      Note that this new behaviour makes "--prune" be a no-op.

That being said, I think that is perhaps a reasonable thing for --prune
to do (and I don't think there is any conflict with the name, because
that is what it _used_ to do before becoming a no-op). But nobody has
actually implemented it.

-Peff