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

From: Junio C Hamano <gitster@pobox.com>
Date: May 23, 2024, 16:09 UTC
Message-ID: <xmqqwmnkv7ay.fsf@gitster.g>
In-Reply-To: <cover.1716451672.git.ps@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

Show 5 quoted lines

>   - It is not safe with concurrent writers. This is the limitation that
> ...
>     none at all, as it may cause users to be less mindful. That's why I
>     decided to just have no solution at all and document the limitation
>     accordingly.

Documenting the limitation is a good place to start. For normal users, would it be sufficient to

 (1) tell your colleagues that this repository is currently closed
     and do not push into it;

 (2) configure "git gc --auto" to never kick in;

 (3) delist the repository from "git maintenance" schedule.

before they try this feature out?

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