Re: Blobs not referenced by file (anymore) are not removed by GC

From: Roberto Tyley <roberto.tyley@gmail.com>
Date: Dec 9, 2014, 22:15 UTC
Message-ID: <CAFY1edY=Ren9krK1-yFoxt92AAushUyqnbt=69hdXMeiBFAK=w@mail.gmail.com>
In-Reply-To: <20141209161133.GA17756@peff.net>

On Tuesday, 9 December 2014, Jeff King <peff@peff.net> wrote:

Show 6 quoted lines

> I actually think filter-branch's "refs/original" is a bit outdated at
> this point. The information is there in the reflogs already, and
> dealing with refs/original often causes confusion in my experience. It
> could probably use a "git filter-branch --restore" or something to
> switch each $ref to $ref@{1} (after making sure that the reflog entry
> was from filter-branch, of course).

Yeah, I'd agree that refs/original can cause confusion.

> Not that I expect you to want to work on filter-branch. :) But maybe
> food for thought for a BFG feature.

I haven't heard much demand for a recover/restore feature on the BFG (I think by the time people get to the BFG, they're pretty sure they want to go ahead with the procedure!) but I'll bear it in mind. Mind you, to make the post-rewrite clean-up easier, I'd be happy to contribute a patch that gives 'gc' a flag to do the equivalent of:

git reflog expire --expire=now --all && git gc --prune=now --aggressive

Maybe:

git gc --purge

??