Hey all, One of my collegues did: git checkout origin/somebranch git complained that they need to specify the name with -b. So they did: git checkout -b origin/somebranch origin/somebranch Git accepts this with no problems, but boy - all hell broke loose. Doing a push or pull gave errors, because "origin/somebranch" is now ambigous (since there is two of them). They can't even: "git checkout -b somebranch origin/somebranch" anymore, since "origin/somebranch" is ambigous. It all got into a mess. I've sort it out now, but I'd like to request that git doesn't so easily let the user shoot themselves in the foot. I propose that creating a branch called "origin/*" or "remotes/*" gives at _least_ a warning, and preferably an error (overrideable with --force for people who really really want to do it) John Tapsell -- 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
