git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 6/8] receive-pack.c: add a receive.preferatomicpush configuration variable

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 30, 2014, 22:03 UTC
Message-ID
<xmqqy4rxtdu5.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CAL=YDWmNXpe=0UxbHD-5pwNW-hdp=Ja1Xy8gXAKcbSkoJhpgRw@mail.gmail.com>
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.
Previous: Ronnie SahlbergNext: Ronnie Sahlberg
Message 15 of 18 in “ref-transaction-send-pack”
  1. 0/8 ref-transaction-send-packRonnie Sahlberg, Oct 21, 2014
  2. 1/8 receive-pack.c: add protocol support to negotiate atomic-pushRonnie Sahlberg, Oct 21, 2014
  3. Junio C HamanoOct 30, 2014
  4. Ronnie SahlbergOct 30, 2014
  5. 2/8 send-pack.c: add an --atomic-push command line argumentRonnie Sahlberg, Oct 21, 2014
  6. Junio C HamanoOct 30, 2014
  7. Ronnie SahlbergOct 30, 2014
  8. 3/8 receive-pack.c: use a single transaction when atomic-push is negotiatedRonnie Sahlberg, Oct 21, 2014
  9. Junio C HamanoOct 30, 2014
  10. 4/8 push.c: add an --atomic-push argumentRonnie Sahlberg, Oct 21, 2014
  11. 5/8 t5543-atomic-push.sh: add basic tests for atomic pushesRonnie Sahlberg, Oct 21, 2014
  12. 6/8 receive-pack.c: add a receive.preferatomicpush configuration variableRonnie Sahlberg, Oct 21, 2014
  13. Junio C HamanoOct 30, 2014
  14. Ronnie SahlbergOct 30, 2014
  15. Junio C HamanoOct 30, 2014
  16. Ronnie SahlbergOct 30, 2014
  17. 7/8 refs.c: add an err argument to create_reflogRonnie Sahlberg, Oct 21, 2014
  18. 8/8 refs.c: add an err argument to create_symrefRonnie Sahlberg, Oct 21, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.