Re: [PATCH v3 9/9] update-ref: implement interactive transaction handling
- From
Patrick Steinhardt <ps@pks.im>
- Date
- Apr 6, 2020, 07:10 UTC
- Message-ID
- <20200406071057.GB5302@tanuki.pks.im>
- In-Reply-To
- <xmqqa73s1njt.fsf@gitster.c.googlers.com>
On Fri, Apr 03, 2020 at 10:33:58AM -0700, Junio C Hamano wrote:
Show 14 quoted lines
> Phillip Wood <phillip.wood123@gmail.com> writes: > > > I found the talk of "non-transactional" sessions a bit confusing > > because the normal --stdin does update all the refs it is given as a > > single transaction, so that if it cannot update one ref none of them > > are updated. If I've understood correctly these changes are about > > coordinating transactions across several repositories. I'm not sure > > how best to convey that in the man page - perhaps we could call them > > single repository transactions and multi repository transaction or > > something. > > FWIW, I described the topic in my "What's cooking" report as adding > an ingredient to implement two-phase commit-style atomic updates > across multiple repositories.
Fair enough. It definitely may serve as a building block for cross-repo transactions, which also is the original intent of this patch series. I'm not sure whether it makes sense to document it as such, as I can imagine usecases acting on a single repository that still want to be in the business of doing two-phase commits.
Patrick