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, 20:11 UTC
Message-ID
<xmqq7fzhuxlh.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1413924400-15418-7-git-send-email-sahlberg@google.com>
Ronnie Sahlberg <sahlberg@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 that says "We take only atomics when a push tries to update more than one", but this one is iffy.

If the receiver accepts non-atomic from older send-pack, those with newer send-pack should have a way to say "the receiving end may prefer atomic, but I choose not to." Is there a way to do so?

And if there is such a way, what value does the preference add to the user experience and the server's operation?

Previous: Ronnie SahlbergNext: Ronnie Sahlberg
Message 13 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.