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

Re: reftable [v6]: new ref storage format

From
Shawn Pearce <spearce@spearce.org>
Date
Aug 7, 2017, 18:30 UTC
Message-ID
<CAJo=hJvsdkrv6uELF0BHxqk4+as8-tr1bdYNHiQ3paTmn=2sRw@mail.gmail.com>
In-Reply-To
<CAGZ79kZO517Bg+O2z3dr+oHqO_av1__FU3h9bP=rhXJUSDnRjA@mail.gmail.com>
On Mon, Aug 7, 2017 at 11:27 AM, Stefan Beller <sbeller@google.com> wrote:
Show 10 quoted lines
> On Sun, Aug 6, 2017 at 6:47 PM, Shawn Pearce <spearce@spearce.org> wrote:
>> 6th iteration of the reftable storage format.
>>
>> You can read a rendered version of this here:
>> https://googlers.googlesource.com/sop/jgit/+/reftable/Documentation/technical/reftable.md
>>
>> The index may be organized into a multi-level index, where ...
>> which may in turn point to either index blocks (3rd level) or ref blocks (leaf level).
>
> So we allow 3 levels at most?

No, its just an example. Large ref sets with small block size need 4 levels. Or more.

> The file format structure marks the indexes '?', should that be
> rather '*' to indicate there can be more than one index block?
Will fix in the next respin of the document, thanks.
Previous: Stefan BellerNext: Stefan Beller
Message 3 of 12 in “Re: reftable [v6]: new ref storage format”
  1. Shawn PearceAug 7, 2017
  2. Stefan BellerAug 7, 2017
  3. Shawn PearceAug 7, 2017
  4. Stefan BellerAug 8, 2017
  5. Jeff KingAug 8, 2017
  6. Junio C HamanoAug 8, 2017
  7. Shawn PearceAug 8, 2017
  8. Junio C HamanoAug 8, 2017
  9. Shawn PearceAug 9, 2017
  10. Junio C HamanoAug 8, 2017
  11. Shawn PearceAug 8, 2017
  12. Michael HaggertyAug 14, 2017

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.