Re: [PATCH] ls-remote: default to 'origin' when no remote specified

Jeff King [off-list ref] writes:

I don't really see a problem with this. The current behavior produces an
error, so it is not as if we are breaking somebody's workflow, and the
only sensible default is the same one used by the other commands.

I'd agree only if "the other commands" default to the same remote;
otherwise as a plumbing, ls-remote should insist that the user be more
explicit.

The only odd-man out that would worry me is "git pull", as I expect
everybody written in C would just use remote_get(NULL).