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

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

From
Jeff King <peff@peff.net>
Date
Mar 24, 2017, 18:45 UTC
Message-ID
<20170324184550.3l6mw4ybynizblsm@sigill.intra.peff.net>
In-Reply-To
<1490375874.745.227.camel@locke.gandi.net>
On Fri, Mar 24, 2017 at 06:17:54PM +0100, Romuald Brunet wrote:
> Added a "push.atomic" option to git-config to allow site-specific
> configuration of the atomic flag of git push

I don't really use --atomic myself, but this seems like a reasonable thing to want, and the implementation looks cleanly done.

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.

-Peff
Previous: Romuald BrunetNext: Jonathan Nieder
Message 2 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.