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

Re: git-unpack-objects

From
MRMarco Roeland <marco.roeland@xs4all.nl>
Date
May 4, 2006, 10:02 UTC
Message-ID
<20060504100237.GA10548@fiberbit.xs4all.nl>
In-Reply-To
<625fc13d0605031731v7b65a738r6fc0169958235928@mail.gmail.com>
On Wednesday May 3rd 2006 Josh Boyer wrote:
Show 7 quoted lines
> >It does. That's what the "-a" (for "all") does.
> 
> Odd.  On one of my repos, I was seeing the correct behavior.  On
> another, there were multiple packs left after doing the 'git repack -a
> -d'.  Were there ever some packing bugs in older versions of git that
> would have maybe produced some packs that wouldn't get deleted or
> something?

Have you checked with "git fsck-objects" that maybe the "remaining" packs contained non-reachable objects like dangling commits from resets or from following volatile branches like +pu?

-- 
Marco Roeland
Previous: Josh BoyerNext: Josh Boyer
Message 8 of 9 in “git-unpack-objects”
  1. Josh BoyerMay 1, 2006
  2. Junio C HamanoMay 1, 2006
  3. Josh BoyerMay 3, 2006
  4. Linus TorvaldsMay 3, 2006
  5. Josh BoyerMay 3, 2006
  6. Linus TorvaldsMay 3, 2006
  7. Josh BoyerMay 4, 2006
  8. Marco RoelandMay 4, 2006
  9. Josh BoyerMay 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.