From: Ronnie Sahlberg <sahlberg@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH 6/8] receive-pack.c: add a receive.preferatomicpush configuration variable
Date: Thu, 30 Oct 2014 15:26:47 -0700 [thread overview]
Message-ID: <CAL=YDWms5geok1j8tQUjHaOVTSG-_zbTob_AVX0GS8cA0rwaSQ@mail.gmail.com> (raw)
In-Reply-To: <xmqqy4rxtdu5.fsf@gitster.dls.corp.google.com>
On Thu, Oct 30, 2014 at 3:03 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Ronnie Sahlberg <sahlberg@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.
>
> As I still do not quite understand why you find that this could be a
> "convenience preference" on the server operator's end, that would be
> my preference, at least until I am convinced why this could be a
> good idea.
>
> Thanks.
>
Ok, I dropped this patch.
Thanks
Ronnie Sahlberg
next prev parent reply other threads:[~2014-10-30 22:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 20:46 [PATCH 0/8] ref-transaction-send-pack Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 1/8] receive-pack.c: add protocol support to negotiate atomic-push Ronnie Sahlberg
2014-10-30 19:59 ` Junio C Hamano
2014-10-30 20:46 ` Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 2/8] send-pack.c: add an --atomic-push command line argument Ronnie Sahlberg
2014-10-30 20:04 ` Junio C Hamano
2014-10-30 21:21 ` Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 3/8] receive-pack.c: use a single transaction when atomic-push is negotiated Ronnie Sahlberg
2014-10-30 20:05 ` Junio C Hamano
2014-10-21 20:46 ` [PATCH 4/8] push.c: add an --atomic-push argument Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 5/8] t5543-atomic-push.sh: add basic tests for atomic pushes Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 6/8] receive-pack.c: add a receive.preferatomicpush configuration variable Ronnie Sahlberg
2014-10-30 20:11 ` Junio C Hamano
2014-10-30 21:36 ` Ronnie Sahlberg
2014-10-30 22:03 ` Junio C Hamano
2014-10-30 22:26 ` Ronnie Sahlberg [this message]
2014-10-21 20:46 ` [PATCH 7/8] refs.c: add an err argument to create_reflog Ronnie Sahlberg
2014-10-21 20:46 ` [PATCH 8/8] refs.c: add an err argument to create_symref Ronnie Sahlberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL=YDWms5geok1j8tQUjHaOVTSG-_zbTob_AVX0GS8cA0rwaSQ@mail.gmail.com' \
--to=sahlberg@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).