Re: [PATCH] Make git-clone --use-separate-remote the default

From: Salikh Zakirov <salikh.zakirov@intel.com>
Date: Nov 24, 2006, 11:56 UTC
Message-ID: <ek6mm5$j2f$1@sea.gmane.org>
In-Reply-To: <7vslg9axzv.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:

Show 12 quoted lines

> 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.

Show 7 quoted lines

> 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.