On 5/4/06, Marco Roeland <marco.roeland@xxxxxxxxx> wrote:
On Wednesday May 3rd 2006 Josh Boyer wrote: > >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?
This was on a kernel repo, so no branches. But dangling commits from resets might have been present. I can't tell now since I undid all that packs and redid them into a single. Thanks for the suggestion though, that sounds like a perfectly reasonable explanation. josh - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html