Re: [PATCH v6 00/42] Use ref transactions for all ref updates

2014-05-13 Thread Jonathan Nieder
Hi, Ronnie Sahlberg wrote: This patch series is based on next and expands on the transaction API. Sorry to take so long to get to this. For the future, it's easier to review patches based on some particular branch that got merged into next, since next is a moving target (series come and go

Re: [PATCH v6 00/42] Use ref transactions for all ref updates

2014-05-05 Thread Michael Haggerty
On 05/01/2014 10:37 PM, Ronnie Sahlberg wrote: This patch series is based on next and expands on the transaction API. [...] Meta-comment: Ronnie, It seems like successive versions of this patch series are growing not only in maturity but also in breadth. That makes it harder to review them.

Re: [PATCH v6 00/42] Use ref transactions for all ref updates

2014-05-05 Thread Ronnie Sahlberg
On Mon, May 5, 2014 at 5:57 AM, Michael Haggerty mhag...@alum.mit.edu wrote: On 05/01/2014 10:37 PM, Ronnie Sahlberg wrote: This patch series is based on next and expands on the transaction API. [...] Meta-comment: Ronnie, It seems like successive versions of this patch series are growing

[PATCH v6 00/42] Use ref transactions for all ref updates

2014-05-01 Thread Ronnie Sahlberg
This patch series is based on next and expands on the transaction API. It converts all ref updates, inside refs.c as well as external, to use the transaction API for updates. This makes most of the ref updates to become atomic when there are failures locking or writing to a ref. This version