Junio C Hamano wrote:
> and if you write
>
> git push $remote master
>
> it is handled exactly as if you wrote:
>
> git push $remote master:master
>
> The manual correctly describes the above, but the issue the fix
> addresses is about what happens to that 'master' string that
> follows the colon, and the 'master' string becomes ambiguous if
> the remote end uses separate-remote layout.
Indeed, the manual describes it correctly.
My point is that this semantics fairly complex
and easy to understand incorrectly.
> Even under separate-remote layout, we would want to be able to
> say:
>
> git push master
>
> to mean we want to push to remote's heads/master when the remote
> has remotes/{origin,blech}/master.
I agree with your main point that 'git push master' should "just work"
for all existing and new repositories, however,
it is very confusing that 'git push master' can update something other than
refs/heads/master, depending on the refs existing in the remote repo.
-
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