Luben Tuikov wrote: > --- Junio C Hamano <junkio@xxxxxxx> wrote: >> Luben Tuikov <ltuikov@xxxxxxxxx> 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. > > 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 - 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