Re: [PATCH v4 00/27] Use ref transactions for all ref updates
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Apr 29, 2014, 21:41 UTC
- Message-ID
- <xmqq4n1bke4b.fsf@gitster.dls.corp.google.com>
- In-Reply-To
- <1398725682-30782-1-git-send-email-sahlberg@google.com>
Ronnie Sahlberg <sahlberg@google.com> writes:
Show 5 quoted lines
> This patch series is based on mhagger/ref-transactions and expands on the > transaction API. It converts all external (outside of refs.c) callers to > use the transaction API for any writes. > This makes most of the ref updates to become atomic when there are failures > locking or writing to a ref.
I think I saw some more comments to be addressed on this round, but I'll try to push it through into 'pu' by attempting to resolve conflicts so that I can ask you to eyeball the result. This series seem to conflict with your own rs/ref-update-check-errors-early topic that is already in 'next'.
If I screwed up the conflict resolution (which is very possible), I may have to ask you to rebase this series on top of acc62aa (which is the merge of rs/ref-update-check-errors-early to 'next'), but I am hoping that conflict resolution I'll push out today will be correct. We'll see.
Thanks.