Jeff King wrote: > > On Wed, Nov 04, 2009 at 07:41:28AM +0100, Sverre Rabbelier wrote: > >> On Wed, Nov 4, 2009 at 07:17, Tim Mazid <timmazid@xxxxxxxxxxx> wrote: >> > So instead of invoking 'git checkout REMOTE/BRANCH', do 'git checkout >> -b >> > BRANCH REMOTE/BRANCH'. >> >> Automagically doing 'git checkout -t remote/branch' when asked to do >> 'git checkout remote/branch' was suggested earlier on the list and I >> think there was even a patch that implemented it, not sure what the >> outcome of the series was. I do remember that Peff was annoyed by it >> at the GitTogether though so it might be a bad idea. > > It's in 'next' now. And for the record, my complaint about its behavior > turned out to be partially because I was an idiot. I am still not > convinced that we won't later regret leaving the stale local branch > sitting around, or that users won't find it confusing to see: > > $ git checkout foo > Branch foo set up to track remote branch foo from origin. > Switched to a new branch 'foo' > > ... time passes ... > > $ git checkout foo > Switched to branch 'foo' > Your branch is behind 'origin/foo' by 1 commit, and can be > fast-forwarded. > Hm. I actually meant inside gitk, not git itself. As in, when you click inside gitk and try to checkout a remote, it automatically creates a tracking branch and checks THAT out instead, whereas command-line git works the same way. Does that even make sense? :P -- View this message in context: http://n2.nabble.com/PATCH-gitk-disable-checkout-of-remote-branch-tp3939363p3943894.html Sent from the git mailing list archive at Nabble.com. -- 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