"Lars Hjemli" <lh@xxxxxxxxxxxxxxxxx> writes: > The magic setup that makes this happen is the following lines in .git/config: > > [remote "origin"] > url = git://git.kernel.org/pub/scm/git/git.git > fetch = +refs/heads/*:refs/remotes/origin/* > > [branch "master"] > remote = origin > merge = refs/heads/master > > > Was this helpful? It would be helpful. Except that nothing whatsoever can be found in .git/config concerning my local and my remote tracking branches. So where is that information _really_ hidden away? .git/FETCH_HEAD maybe? It also appears that doing git-checkout --track -b mybranch origin on a git.git clone does _not_ create a tracking branch. I can't figure out what I could specify as an origin to create a tracking branch that would get reflected in .git/FETCH_HEAD. What gives? -- David Kastrup, Kriemhildstr. 15, 44793 Bochum - 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
