Re: [PATCH v3 06/12] refs API: pass the "lock OID" to reflog "prepare"

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 21, 2021, 17:47 UTC
Message-ID: <xmqqy29zd0dv.fsf@gitster.g>
In-Reply-To: <xmqq35s7efb3.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

> This obviously breaks the latest round of reftable topic, as it
> still wants this type to take const oid, and I do not think using
> on-filesystem lock as if we are using the files backend is not a
> good solution.

Sorry for redundant negation. "I do not think it is a good solution to have everybody pretend as if they are files backend when they lock refs." was what I meant.

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