git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Avery Pennarun <apenwarr@gmail.com>
Date
Apr 24, 2008, 16:59 UTC
Message-ID
<32541b130804240959y3b05d4b5u67ac7a7c14bf187e@mail.gmail.com>
In-Reply-To
<20080424161407.GA23737@sigill.intra.peff.net>
On 4/24/08, Jeff King <peff@peff.net> wrote:
> 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.
Perhaps.
>  But if the note were moved to git-prune, it would be natural to mention
>  git-reflog there. What do you think?

I gather there's a movement in recent git versions (sorry, I only tuned in recently) to encourage people to use git-gc instead of git-prune in almost all cases. The reasons I ever looked at git-prune at all was that git-gc mentioned it in "See Also", and because "git-prune" sounded more obviously like what I wanted than "git-gc" when I looked at "man git".

Adding git-gc *and* git-reflog as See Also entries in git-prune would make sense to me.

Avery
Previous: Jeff KingNext: Jeff King
Message 8 of 12 in “git-gc doesn't clean up leftover objects after git-filter-branch unless you clone first”
  1. Avery PennarunApr 23, 2008
  2. Junio C HamanoApr 23, 2008
  3. Avery PennarunApr 23, 2008
  4. Jeff KingApr 23, 2008
  5. Jeff KingApr 24, 2008
  6. Avery PennarunApr 24, 2008
  7. Jeff KingApr 24, 2008
  8. Avery PennarunApr 24, 2008
  9. Documentation: point git-prune users to git-gcJeff King, Apr 29, 2008
  10. Junio C HamanoApr 29, 2008
  11. Jeff KingApr 29, 2008
  12. Junio C HamanoApr 30, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.