Re: [PATCH resend] make "git push" update origin and mirrors, "git push --mirror" update mirrors

[Jeff King <peff@peff.net>]

On Sun, Apr 27, 2008 at 01:34:46PM -0400, Shawn O. Pearce wrote:

> Just take the above as the rantings of someone who knows git a
> little too well, and has tried to teach it to people who don't,
> and they all have asked about the funny (to them) need for origin
> in git-pull/git-push command line sometimes (no refspecs) and not
> others (with refspecs).

I know git pretty well, and I find that particular distinction (that is,
needing to specify the remote if using refspecs, but not otherwise)
annoying.  And it _is_ a bit funny, but it has nothing to do with
concepts. It is purely a syntactic issue that relying on order of
arguments means you can't default earlier ones but specify later ones.

Whether you hit this particular syntactic funniness depends totally on
your workflow. If you don't tend to default that particular argument,
then you won't see it. But there are plenty of workflows where you
never need to specify a remote, and then typing "git push master:foo"
makes you stop and blink for a second when it fails.

Of course, I don't think there is a reasonable fix now, short of "git
push --ref master:foo".

-Peff