Re: [PATCH 04/13] refs: expose peeled object ID via the iterator

From: Patrick Steinhardt <ps@pks.im>
Date: Oct 8, 2025, 13:45 UTC
Message-ID: <aOZq3HlVV7tF4VSJ@pks.im>
In-Reply-To: <CAOLa=ZRQuLa_xD8GzynHNmNZuyoJeK9dCBOKbUfkCES4ejG0OA@mail.gmail.com>

On Tue, Oct 07, 2025 at 07:52:43AM -0700, Karthik Nayak wrote:

Show 9 quoted lines

> Patrick Steinhardt <ps@pks.im> writes:
> 
> > Both the "files" and "reftable" backend are able to store peeled values
> > for tags in the respective formats. This allows for a more efficient
> > lookup of the target object of such a tag without having to manually
> > peel via the object database.
> >
> 
> In the 'files' backend, I thought only packed-refs store peeled values?

Yup, peeled values may or may not be available with the "files" backend, depending on whether or not a reference is packed. But the paragraph doesn't really contradict this, does it?

Patrick

$ 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.