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

Re: [PATCH] pack-format: correct multi-pack-index description

From
Johannes Berg <johannes@sipsolutions.net>
Date
Feb 10, 2020, 14:22 UTC
Message-ID
<526a7a3d8d135c9b97890c1c238ca5baaa138c3c.camel@sipsolutions.net>
In-Reply-To
<8d50143b-adb9-c642-5ca6-d51662c37dda@gmail.com>
On Mon, 2020-02-10 at 09:18 -0500, Derrick Stolee wrote:
> 
> Thank you for finding this doc bug. This is a very subtle point,
> and you have described it very clearly.

I was going back and forth on the wording a bit, glad I found something that you think is a good description :)

Are you familiar with the multi-pack-index and how it's used, by any chance?

I came here from bup (https://github.com/bup/bup/) and needed a way to store the offset to find objects in "pure bup", today it only stores object *presence* and *pack* in its multi-index, but not the offset.

However, it seems to do a bit better in terms of not requiring a single multi-index, but instead storing it in midx-*.midx files and multiple can describe the repository state. Why wasn't something like that done for git as well? It's a bit annoying to have to recreate the full midx every time a pack file is added, and searching in two or three midx files wouldn't really be a big deal?

Anyway, that's just an aside, but during all this investigation I stumbled across this small inconsistency - I'm glad the docs exist at all! :-)

Thanks, johannes

Previous: Derrick StoleeNext: Derrick Stolee
Message 3 of 8 in “pack-format: correct multi-pack-index description”
  1. pack-format: correct multi-pack-index descriptionJohannes Berg, Feb 7, 2020
  2. Derrick StoleeFeb 10, 2020
  3. Johannes BergFeb 10, 2020
  4. Derrick StoleeFeb 10, 2020
  5. Johannes BergFeb 10, 2020
  6. Derrick StoleeFeb 10, 2020
  7. Johannes BergFeb 10, 2020
  8. Junio C HamanoFeb 10, 2020

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.