Re: [PATCH v5 0/9] refs: fix migration of reflog entries

From: Jeff King <peff@peff.net>
Date: Aug 5, 2025, 18:47 UTC
Message-ID: <20250805184712.GA1345110@coredump.intra.peff.net>
In-Reply-To: <20250805-pks-reflog-append-v5-0-050997db09d5@pks.im>

On Tue, Aug 05, 2025 at 05:11:30PM +0200, Patrick Steinhardt wrote:

Show 5 quoted lines

> Changes in v5:
>   - Revert back to the logic that aborts the transaction if we see a
>     racy HEAD update. It's the pragmatic thing to do for an edge case
>     that is very unlikely to ever happen.
>   - Link to v4: https://lore.kernel.org/r/20250804-pks-reflog-append-v4-0-13213fef7200@pks.im

Thanks, this makes sense to me. I hadn't reviewed the whole series very thoroughly, but I think others did. And certainly this version addresses all of the discussion I did participate in.

-Peff

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