Re: [PATCH v3 2/9] refs/reftable: handle reloading stacks in the reftable backend

From: Junio C Hamano <gitster@pobox.com>
Date: Nov 26, 2024, 00:31 UTC
Message-ID: <xmqqa5dm4yzm.fsf@gitster.g>
In-Reply-To: <20241125-pks-reftable-backend-reuse-iter-v3-2-1d7b658e3e9e@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

> +	 * On the other hand, reloading that stack without locking it feels
> +	 * wrong to, as the value of "HEAD" could be modified concurrently at
> +	 * any point in time.
> +	 */

"wrong to," -> "wrong too,", probably.

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