Junio C Hamano <gitster@xxxxxxxxx> writes: > Karthik Nayak <karthik.188@xxxxxxxxx> writes: > >> Git's reference updates are traditionally all or nothing - when >> updating multiple references in a transaction, either all updates >> succeed or none do. > > I am quite confused. In the beginning (traditionally), there was no > transaction to speak of. You try to update two refs at the same > time, we did best effort but that was never atomic. Later we > introduced transactions to optionally make the changes all-or-none. > > So, if you want "I have these N updates, but I do not care if some > of them have to fail---just make your best effort to update as many > of them as you can", why are you still doing a transaction? > > Perhaps it is merely the phrasing that makes this proposal > confusing. If presented as "non-transactional batched updates", > perhaps it may have been more palatable. I dunno, but "partial > transaction" does not quite sound like a transaction, at least to > me. That's fair. There was also some discussion earlier around this [1]. It is in indeed batched updates which can allow failures, but it is built on top of the transaction infrastructure in the refs subsystem. Perhaps the best way would be to use the transaction interface under the hood, but present this feature as 'batched updates' to users, so there is no confusion between the two. [1]: 4beb0359-763d-425d-b416-ac40bda59e2e@xxxxxxxxx
Attachment:
signature.asc
Description: PGP signature
