From: Patrick Steinhardt <ps@pks.im>
Date: Fri, 24 May 2024 07:33:56 GMT
Subject: Re: [PATCH 0/9] refs: ref storage format migrations
Message-ID: <ZlBC5O4CHqrx1di7@tanuki>
In-Reply-To: <xmqqwmnkv7ay.fsf@gitster.g>

On Thu, May 23, 2024 at 09:09:41AM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks.im> writes:
> 
> >   - 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?

I think (2) wouldn't even be needed. Auto-GC only kicks in when there is
a write in the repository, and if both (1) and (3) are true then there
are none. But other than that yes, (1) and (3) should be sufficient.

Patrick