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 24, 2008, 16:14 UTC
Message-ID: <20080424161407.GA23737@sigill.intra.peff.net>
In-Reply-To: <32541b130804240843k471ecfeteb1008c44a56808b@mail.gmail.com>

On Thu, Apr 24, 2008 at 11:43:55AM -0400, Avery Pennarun wrote:

Show 8 quoted lines

> >  +If you are expecting some objects to be collected and it isn't, check
> >  +all of those locations and decide whether it makes sense in your case to
> >  +remove those references.
> >  +
> 
> This information would have helped me quite a bit when I first
> encountered this problem.  It would be nice if it also showed up under
> git-prune (since git-gc doesn't delete anything itself, if I

Hmm, maybe it would make sense to put that note in git-prune, with a note in git-gc to look at the prune page.

> understand correctly).  Also a link to some information about reflogs
> (even just to "see also" git-reflog) would help, since I didn't hear
> about reflogs at all until after I joined the mailing list.

$ grep -A6 See.Also Documentation/git-gc.txt See Also -------- linkgit:git-prune[1] linkgit:git-reflog[1] linkgit:git-repack[1] linkgit:git-rerere[1]

But if the note were moved to git-prune, it would be natural to mention git-reflog there. What do you think?

-Peff