Patrick Steinhardt <ps@xxxxxx> writes: > 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.
