Re: git-gc doesn't clean up leftover objects after git-filter-branch unless you clone first

From: Jeff King <peff@peff.net>
Date: Apr 23, 2008, 22:13 UTC
Message-ID: <20080423221316.GE30057@sigill.intra.peff.net>
In-Reply-To: <7vve28sdys.fsf@gitster.siamese.dyndns.org>

On Wed, Apr 23, 2008 at 10:00:59AM -0700, Junio C Hamano wrote:

> - Teach people that leftover cruft is nothing to worry about.

But it _is_ something to worry about in some particular situations. For run-of-the-mill rebasing, sure, ignore it. But this question usually comes up because the user did something like:

  1. import from foreign SCM or other source
  2. realize massive, history-wide mistake; git filter-branch
     to fix up the changes
  3. wonder why git is using twice as much space as it needs to; with
     a repository in the hundreds or thousands of megs, this can get
     really annoying (either because of wasted space, or because some
     operations, like "git repack -a" actually do per-object work).

-Peff