Michael S. Tsirkin wrote: > Quoting r. Junio C Hamano <junkio@xxxxxxx>: [...] >> I have been hesitant to claim that it does not make any sense to >> use more than one tracking branch for the same remote branch, >> because the only reason I might say so is because I haven't >> thought of a good usage pattern to do so. >> >> But apparently you do use more than one local branch to keep >> track of one remote branch. How do you use it for? Do you feel >> it is a good feature to be able to do that, or do you think it >> is just a mistake and more sensible error message is what we >> would really want? >> > > Well, what I was *trying* to do is simply add a more descriptive name for > the linus master branch to my existing tree. > So it seemed like an obvious idea to add > > Pull: master:origin > Pull: master:linus_master Couldn't you do this via symlinks or symrefs? BTW. Do we support symrefs other than HEAD, and does reflog works with symref heads, and symlinked heads? -- 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