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

Re: git-pack-redundant returns the most containing pack

From
Lukas Sandström <lukass@etek.chalmers.se>
Date
Nov 16, 2005, 23:23 UTC
Message-ID
<437BBF5D.5040105@etek.chalmers.se>
In-Reply-To
<20051116230956.GA21444@steel.home>
Alex Riesen wrote:
Show 7 quoted lines
> ...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.

Previous: Alex RiesenNext: Alex Riesen
Message 2 of 4 in “git-pack-redundant returns the most containing pack”
  1. Alex RiesenNov 16, 2005
  2. Lukas SandströmNov 16, 2005
  3. Alex RiesenNov 17, 2005
  4. Alex RiesenNov 17, 2005

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.