Re: Dangling blob after git gc

From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Nov 27, 2008, 13:46 UTC
Message-ID: <vpqzljlnuwo.fsf@bauges.imag.fr>
In-Reply-To: <20081127133027.GW4746@genesis.frugalware.org>

Miklos Vajna <vmiklos@frugalware.org> writes:

Show 5 quoted lines

> The commits are probably due to reflogs, that's OK. But why do I have a
> dangling blob after git gc? The interesting part is that as you can see
> most of them is removed, but not all.
>
> Any ideas? :)

from man git-gc:

     The optional configuration variable gc.pruneExpire controls
     how old the unreferenced loose objects have to be before
     they are pruned. The default is "2 weeks ago".

Git can hardly know for sure whether a dangling object is actually a temporary object used by another instance of git or actually an unused object. Older versions of Git required you to explicitely say --prune to mean "OK, _I_ am sure, you can prune the objects", newer do it the safe way by removing only objects old enough.

-- 
Matthieu