Patrick Steinhardt <ps@xxxxxx> 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?
