From: Junio C Hamano <junkio@cox.net>
Date: Tue, 02 Jan 2007 03:36:08 GMT
Subject: Re: [PATCH] Documentation: update git-pull.txt for clone's new default behavior
Message-ID: <7vy7omyuaf.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <405044.6078.qm@web31809.mail.mud.yahoo.com>

Luben Tuikov <ltuikov@yahoo.com> writes:

> Questions:
>
> What is the reasonining of defining branch.<name>.merge to point
> to the "remote's setup"?

See list archives.  

Because you are not required to use remote tracking branches.
By the way, I think we allow the name of the remote tracking
branch as well, but we do not advertise it -- always using
remote's name consistently is much less confusing.

> The reasoning is that the remote's setup should only leak into
> [remote] and no further.  I.e. [remote] is the only one concerned
> with the mapping between the remote repo and the local repo.

No.  Remote is not about mapping -- if mapping is there you can
talk about it, but that is optional.