Re: [PATCH 0/9] refs: ref storage format migrations

From: Junio C Hamano <gitster@pobox.com>
Date: May 28, 2024, 16:16 UTC
Message-ID: <xmqqmso97vzp.fsf@gitster.g>
In-Reply-To: <ZlVoCnojAiShmtRg@tanuki>

Patrick Steinhardt <ps@pks.im> writes:

Show 8 quoted lines

> It is documented as part of the new git-refs(1) man page, in the "Known
> limitations" section:
>
>     * There is no way to block concurrent writes to the repository during an
>       ongoing migration. Concurrent writes can lead to an inconsistent migrated
>       state. Users are expected to block writes on a higher level. If your
>       repository is registered for scheduled maintenance, it is recommended to
>       unregister it first with git-maintenance(1).

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