Jeff King <p...@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.
