Daniel Barkalow wrote: > The upshot of the messages should be: > > $ git checkout origin/master > Since you can't actually change "origin/master" yourself, you'll just > be sightseeing unless you create a local branch to hold new local work. > > $ git branch > * (not a local branch, but "origin/master") > > $ git commit > You've been sightseeing "origin/master". The commit can't change that > value, so your commit isn't held in any branch. If you want to create > a branch to hold it, here's how. I appreciate such a message for git branch as a user. Today I had the following problem: I wanted to compile Qt Creator 1.3 from their repository. I cloned it with git clone and then issued git checkout origin/1.3.0-beta. First there came a the warning and I was not sure whether the checkout succeeded at all. I had to ask in the IRC channel whether the checkout was ok. But then I was not able to verify that the checkout indeed matched the 1.3.0-beta. "git status" and "git branch" did not help here. Having an improved "git branch" would help a lot, especially if one returns some weeks later to the directory and wants to know what the checkout is. Christoph -- 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