From: Karl Hasselström <kha@treskal.com>
Date: Fri, 02 May 2008 08:22:32 GMT
Subject: Re: [PATCH] git-bisect.sh: don't accidentally override existing branch "bisect"
Message-ID: <20080502082232.GA20020@diana.vm.bytemark.co.uk>
In-Reply-To: <20080430164613.28314.qmail@b31db398e1accc.315fe32.mid.smarden.org>

On 2008-04-30 16:46:13 +0000, Gerrit Pape wrote:

> If a branch named "bisect" or "new-bisect" already was created in
> the repo by other means than git bisect, doing a git bisect used to
> override the branch without a warning. Now if the branch "bisect" or
> "new-bisect" already exists, and it was not created by git bisect
> itself, git bisect start fails with an appropriate error message.
> Additionally, if checking out a new bisect state fails due to a
> merge problem, git bisect cleans up the temporary branch
> "new-bisect".

Makes me wonder why bisect has to use a branch at all, and not just a
detached HEAD ... I seem to recall this having been discussed before,
but I can't find it now.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle