"W. Trevor King" <wking@tremily.us> writes: > On Sun, Jul 13, 2014 at 09:30:56AM -0300, David Bremner wrote: >> I consider it a useful feature that it works without the user >> configuring a local branch. I agree that in more complex setups >> this ambiguity is not as nice, but I'd rather it was only the >> minority of users with unusual setups (e.g. multiple remotes) have >> to do configuration. > > I could work up a patch that tried ‘git show-ref -s config’ first, and > only fell back to ‘show-ref -s --heads’ if there were multiple > matches. That way folks with only origin/config wouldn't need a local > branch, but folks with multiple config-carrying remotes (or a single > config-carrying remote and a local branch) would have to have a local > config to break the tie. That's possible, and not *too* complicated, > but I personally prefer the consistency of just requiring a local > config branch. It might be simpler to implement (and understand) to try first the local config branch and then fall back to "origin/config". d