On Mon, Feb 19, 2007 at 07:13:59PM +0100, Raimund Bauer wrote: > I think it's a good idea to not list remote branches in 'git branch' > output per default, but imho we should make an exception for the branch > the user is currently on. > Currently when I do 'git checkout origin/next' the checkout works fine > and I get the warning about the remote branch, but an informational > query 'git branch' right after that says > > * (no branch) > master > > 'git branch -r' also doesn't mark me as being on origin/next. That's because you're not really "on" origin/next. Your currently checked-out state happens to be the same as the state that origin/next points at, but that's not quite the same thing. The main difference being that if you commit something, origin/next won't be moved forward to point at the new commit. > Maybe we could query the remote-branches for a matching ref this case? If that's what you want you could use e.g. git describe --all --b. - 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