Re: [PATCH] remote-curl: pass on atomic capability to remote side

2019-10-17 Thread Junio C Hamano
"brian m. carlson" writes: > Yeah, my default editor configuration for AsciiDoc is two spaces. I > noticed that Junio's already picked it up for next, but I'll send a v2 > with this fixed in case he wants to merge the fixed version to master > instead. > > If it's more convenient, I can send a f

Re: [PATCH] remote-curl: pass on atomic capability to remote side

2019-10-16 Thread brian m. carlson
On 2019-10-15 at 16:40:29, Jeff King wrote: > On Tue, Oct 15, 2019 at 01:07:59AM +, brian m. carlson wrote: > > diff --git a/Documentation/gitremote-helpers.txt > > b/Documentation/gitremote-helpers.txt > > index a5c3c04371..670d72c174 100644 > > --- a/Documentation/gitremote-helpers.txt > > +

Re: [PATCH] remote-curl: pass on atomic capability to remote side

2019-10-15 Thread Jeff King
On Tue, Oct 15, 2019 at 01:07:59AM +, brian m. carlson wrote: > Fix this by passing the option from the transport code through to remote > helpers, and from the HTTP remote helper down to send-pack. With this > change, we can detect if the server side rejects the push and report > back approp

[PATCH] remote-curl: pass on atomic capability to remote side

2019-10-14 Thread brian m. carlson
When pushing more than one reference with the --atomic option, the server is supposed to perform a single atomic transaction to update the references, leaving them either all to succeed or all to fail. This works fine when pushing locally or over SSH, but when pushing over HTTP, we fail to pass th