On 2012-12-17, Tomas Carnecky <tomas.carnecky@xxxxxxxxx> wrote: > On Mon, 17 Dec 2012 16:13:08 +1100, Andrew Ardill > <andrew.ardill@xxxxxxxxx> wrote: >> On 17 December 2012 16:06, Woody Wu <narkewoody@xxxxxxxxx> wrote: >> > 1. git checkout foo. By this command, I think I am checking out >> > files in my local branch named foo, and after that I also switch to >> > the branch. Right? >> >> Correct. Your working directory (files) switch over to whatever your >> local branch 'foo' points to, and your HEAD is updated to point to >> your local branch 'foo'. Unless something goes wrong/you have >> conflicting files/uncommitted changes etc. > > 'git checkout foo' has special meaning if a local branch with that > name doesn't exist but there is a remote branch with that name. In > that case it's equivalent to: git checkout -t -b foo origin/foo. > Because that's what people usually want. I think this is what exactly happened to me in the first time I got the 'foo'. One new thing to me is the '-t'. I am not sure wether the '-t' was used or not in the background. How do I check the 'upstream' relationships? Is there any file under .git recoreded that kind of information? -- woody I can't go back to yesterday - because I was a different person then. -- 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