Re: [PATCH v4 0/3] replay: make atomic ref updates the default

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 25, 2025, 16:57 UTC
Message-ID: <xmqqzf9encl1.fsf@gitster.g>
In-Reply-To: <xmqq7bwlv4jh.fsf@gitster.g>

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

Show 10 quoted lines

> Siddharth Asthana <siddharthasthana31@gmail.com> writes:
>
>> This is v4 of the git-replay atomic updates series.
>> ...
> I didn't see anything glaringly wrong in this round, even though I
> picked a couple of small nits in one patch, so we might want a
> hopefully small and final reroll before marking the topic for
> 'next'.
>
> Is everybody else happy with this iteration otherwise?

There are a few actionable comments pointing out typos and style glitches for this iteration. I'll mark the topic as expecting a hopefully small and final reroll in the next issue of "What's cooking" report.

Thanks.

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