Ronnie Sahlberg sahlb...@google.com writes:
Add receive.preferatomicpush setting to receive-pack.c. This triggers
a new capability prefer-atomic-push to be sent back to the send-pack
client, requesting the client, if it supports it, to request
an atomic push.
I can understand a configuration
On Thu, Oct 30, 2014 at 1:11 PM, Junio C Hamano gits...@pobox.com wrote:
Ronnie Sahlberg sahlb...@google.com writes:
Add receive.preferatomicpush setting to receive-pack.c. This triggers
a new capability prefer-atomic-push to be sent back to the send-pack
client, requesting the client, if it
Ronnie Sahlberg sahlb...@google.com writes:
At some stage it may becomes too many preferences and over-engineered.
Maybe I should drop this patch and then just require the plain if you
want a push to be atomic, then use --atomic-push. end. and we have
simple and easy to understand semantics.
On Thu, Oct 30, 2014 at 3:03 PM, Junio C Hamano gits...@pobox.com wrote:
Ronnie Sahlberg sahlb...@google.com writes:
At some stage it may becomes too many preferences and over-engineered.
Maybe I should drop this patch and then just require the plain if you
want a push to be atomic, then use
Add receive.preferatomicpush setting to receive-pack.c. This triggers
a new capability prefer-atomic-push to be sent back to the send-pack
client, requesting the client, if it supports it, to request
an atomic push.
This is an alternative way to trigger an atomic push instead of having
to rely of
5 matches
Mail list logo
