Package: git-core Version: 1:1.5.5-1 Severity: grave
[EMAIL PROTECTED]:~/git/geode$ git branch bisect db3d7edfded94d176e89b369dad6f01ffca4bd8b [EMAIL PROTECTED]:~/git/geode$ git checkout bisect Switched to branch "bisect" [EMAIL PROTECTED]:~/git/geode$ git branch * bisect linux-2.6 master no-ofw [EMAIL PROTECTED]:~/git/geode$ git log|egrep '(6c7df20ed6591822a52979a29032b7886b705e8a|db3d7edfded94d176e89b369dad6f01ffca4bd8b)' commit db3d7edfded94d176e89b369dad6f01ffca4bd8b commit 6c7df20ed6591822a52979a29032b7886b705e8a [EMAIL PROTECTED]:~/git/geode$ git bisect start bisect 6c7df20ed6591822a52979a29032b7886b705e8a Switched to branch "master" [EMAIL PROTECTED]:~/git/geode$ git log|egrep '(6c7df20ed6591822a52979a29032b7886b705e8a|db3d7edfded94d176e89b369dad6f01ffca4bd8b)' [EMAIL PROTECTED]:~/git/geode$ git branch linux-2.6 * master no-ofw [EMAIL PROTECTED]:~/git/geode$ git bisect reset Already on "master" [EMAIL PROTECTED]:~/git/geode$ As you can see, not only has git-bisect failed to bisect the branch that I've entitled 'bisect', but it has also switched me back to the master branch _and_ deleted the 'bisect' branch. This made me most unhappy when I discovered this (luckily, I had the sha1 in my bash history). I do believe it's related to the branch name. If I use the name 'litterbox', it will happily go in there rather than soiling the rug: [EMAIL PROTECTED]:~/git/geode$ git branch litterbox db3d7edfded94d176e89b369dad6f01ffca4bd8b [EMAIL PROTECTED]:~/git/geode$ git checkout litterbox Switched to branch "litterbox" [EMAIL PROTECTED]:~/git/geode$ git branch linux-2.6 * litterbox master no-ofw [EMAIL PROTECTED]:~/git/geode$ git bisect start litterbox 6c7df20ed6591822a52979a29032b7886b705e8a Bisecting: 3567 revisions left to test after this [e80ab411e589e00550e2e6e5a6a02d59cc730357] Merge git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-2.6 [EMAIL PROTECTED]:~/git/geode$ Weird, eh? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
