On Sat, 04 Aug 2007 16:01:55 +0200 David Kastrup <dak@gnu.org> wrote:Sure, that's one way to describe it; perhaps it would be best if we switched to that nomenclature in the documentation. This is easy to test, and the answer is that no tracking is set up. You must supply the remote-tracking-branch on the command line with the --track option to git branch. Actually I realized that with a new enough version of Git, --track is implied. It's not a problem, you could just add an appropriate [branch...] section in your .git/config. Actually looking at a typical branch section is even more confusing to me: $ git branch fudge origin/fix1 adds this to the .git/config: [branch "fudge"] remote = origin merge = refs/heads/fix1 The config file does not record the remote-tracking-branch, instead it explicitly records the remote repository information. So it sure appears that if you add the --track option, it _does_ make the local branch track a remote directly. Thus it's hard to call it anything but what you labelled it, a local tracking-branch. While I thought i had a handle on this, i'm now officially more confused than you; hopefully someone with knowledge of the guts of Git will speak up. Junio Help! Sean - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Linus Torvalds | Linux 2.6.27-rc5 |
| Greg Kroah-Hartman | [PATCH 007/196] Chinese: add translation of stable_kernel_rules.txt |
| Kamalesh Babulal | [Build Failure] 2.6.25-rc5-mm1 Build fails with allmodconfig probe_4drives undefined |
| Gabriel C | Re: Linus 2.6.23-rc1 |
| David Woodhouse | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
git: | |
