From: Lukas Sandström <lukass@etek.chalmers.se>
Date: Wed, 16 Nov 2005 23:23:09 GMT
Subject: Re: git-pack-redundant returns the most containing pack
Message-ID: <437BBF5D.5040105@etek.chalmers.se>
In-Reply-To: <20051116230956.GA21444@steel.home>

Alex Riesen wrote:
> ...which very confusing: "git-repack -a -d" leaves the repository with
> exactly the same packs as before, by creating a super-pack, and then
> happily removing it, because pack-redundant returns the newly created
> pack!
> 
> So, even if it is logically correct, it's hardly useful in practice.
> 

That's bad. Your new pack should contain some objects not present in
the older packfiles and thus it shouldn't be removed, unless there
were no new objects to pack. 

If no new objects were packed, the sum of the old packs might be smaller 
than the new superpack, or the old packs could contain unreachable objects,
which makes git-pack-redundant unable to detect that they should be removed.

Could you try updating to the latest snapshot? There was a bug in a
list handling function which was fixed recently, perhaps your problem
is related.