tags 478647 + patch severity 478647 important quit On Tue, Apr 29, 2008 at 10:20:23PM -0400, Andres Salomon wrote: > 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:
Yes, it's the magic branch names "bisect" and "new-bisect", here's a patch to protect againt the accidental override http://git.kernel.org/?p=git/git.git;a=commitdiff;h=ee831f7 With somewhat newer git, there's always the reflog that enables you to restore branches and objects, see git-reflog(1) and the -g option to git-log(1). Regards, Gerrit. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
