Thread (4 messages) flat view 4 messages, 3 authors, 2016-06-15

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

From: Jakub Narebski <hidden>
Date: 2016-06-15 22:42:47

Luben Tuikov wrote:
quoted hunk ↗ jump to hunk
--- Junio C Hamano <junkio@cox.net> wrote:
quoted
Luben Tuikov [off-list ref] writes:
quoted
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.
Then why does it point to the _remote_ mapping?  One shouldn't
care what it is, and how it looks in the remote repo.  That is
handled by [remote].  In [branch] I shouldn't have to have any
absolute references, i.e. branch.<name>.remote points to [remote],
and branch.<name>.merge should only give a _branch_ name,
whose remote-to-local mapping (which preserves the branch name)
can be found by dereferencing branch.<name>.remote to get to
remote.<rname>.fetch.
Once again: if you _don't_ have _local_ tracking branch, so you _must_
use _remote_ name.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help