Re: [PATCH] Documentation: update git-pull.txt for clone's new default behavior

Luben Tuikov [off-list ref] 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.