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

Re: [PATCH] push: allow atomic flag via configuration

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 24, 2017, 19:29 UTC
Message-ID
<xmqqmvca79sh.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170324184550.3l6mw4ybynizblsm@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
> My one question would be whether people would want this to actually be
> specific to a particular remote, and not just on for a given repository
> (your "site-specific" in the description made me think of that). In that
> case it would be better as part of the remote.* config.
Yeah, I had the same reaction.

Conceptually, this sits next to remote.*.push that defines which set of refs are sent by default, and remote.<name>.pushAtomic does make sense. If (and only if) it turns out to be cumbersome for somebody to set the configuration for each and every remote, it is OK to also add push.atomic to serve as a fallback for remote.*.pushAtomic, I would think, but adding only push.atomic feels somewhat backwards.

Previous: Jeff KingNext: Romuald Brunet
Message 5 of 10 in “push: allow atomic flag via configuration”
  1. push: allow atomic flag via configurationRomuald Brunet, Mar 24, 2017
  2. Jeff KingMar 24, 2017
  3. Jonathan NiederMar 24, 2017
  4. Jeff KingMar 24, 2017
  5. Junio C HamanoMar 24, 2017
  6. Romuald BrunetMar 27, 2017
  7. Jonathan NiederMar 28, 2017
  8. Ævar Arnfjörð BjarmasonMar 27, 2017
  9. Ævar Arnfjörð BjarmasonMar 27, 2017
  10. Junio C HamanoMar 27, 2017

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.