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

Re: git-repack && git-prune-packed isn't doing it's job anymore?

From
Junio C Hamano <junkio@cox.net>
Date
Mar 4, 2006, 00:53 UTC
Message-ID
<7v64mv2for.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<46a038f90603031629qbbb287ckd8da1ef56a831dba@mail.gmail.com>
"Martin Langhoff" <martin.langhoff@gmail.com> writes:
Show 13 quoted lines
> $ find .git/objects -type f | grep -v pack | wc -l
>     3297
> $ git-repack && git-prune-packed
> Generating pack...
> Done counting 664 objects.
> Deltifying 664 objects.
>  100% (664/664) done
> Writing 664 objects.
>  100% (664/664) done
> Total 664, written 664 (delta 384), reused 0 (delta 0)
> Pack pack-f38c51a5d5194d6a2f6e711586b9a51980c8d524 created.
> $ find .git/objects -type f | grep -v pack | wc -l
>     2583

The last one would be "git count-objects", but repack packs things that are reachable from your refs and prune-packed removes what are in packs, so perhaps these are unreachable objects? I'd imagine fsck-objects would say they are dangling.

If that is the case, "git prune" would be the right tool to use.
And this is not something that changed recently.
Previous: Martin LanghoffNext: Martin Langhoff
Message 2 of 3 in “git-repack && git-prune-packed isn't doing it's job anymore?”
  1. Martin LanghoffMar 4, 2006
  2. Junio C HamanoMar 4, 2006
  3. Martin LanghoffMar 4, 2006

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.