On Mon, Mar 18, 2013 at 10:28:59PM +0530, Ramkumar Ramachandra wrote: > This has irritated me for a long time. I often end up doing: > > $ git push master:master +pu:pu Me too. > Is there a reason for the remote not being optional, or are we just > waiting for a patch? The only problem I can foresee is very minor: > there is a ref with the same name as a remote; in this case, we'd have > to specify both the remote and the ref. I think the ambiguity is a little more complex than that, because we cannot enumerate the universe of all remotes. Keep in mind that we can take either a configured remote or a URL (or ssh host). So what does: git push foo:bar mean? Is it pushing "refs/heads/foo" to "refs/heads/bar" on "origin"? Or is it using the default refspecs to push to the "bar" repo on the host "foo" over ssh? So you would need some heuristics based on whether something was a valid refspec, or could be a valid remote name or URL. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html