Thomas Rast wrote: > Artur Skawina wrote: >> + git checkout -f -b branch-g90bc1a6 askern/release >> fatal: git checkout: branch branch-g90bc1a6 already exists > > This bisects to > > commit 352eadc40024b141e1295693654ec20cc123844f > Author: Daniel Barkalow <barkalow@xxxxxxxxxxxx> > Date: Sun Sep 21 14:36:06 2008 -0400 > > Check early that a new branch is new and valid > Not sure this is a bug though. If we allow branch names that are well, it didn't say it didn't like the name, and sent me looking for bugs in my scripts for quite a while, until i realized what's going on... > ambiguous to rev-parse, what do they resolve to? E.g., in the > presence of only 'master', 'master-g01234567' is defined to be the > same as 01234567. What is it if you also have a *branch* called > 'master-g01234567'? I'd expect the branch namespace to take precedence, unless branches ending in -g01234567 are illegal, but that seems like an odd limitation. Note that currently this works: + ( cd /tmp/build-tree/ && git checkout -f whatever/random-name-g90bc1a6 ) HEAD is now at 90bc1a6... Merge branch 'upstream' of git://ftp.linux-mips.org/pub/scm/upstream-linus which doesn't seem right either. artur -- 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