From: Michael Witten <mfwitten@gmail.com>
Date: Sun, 22 May 2011 19:41:07 GMT
Subject: Re: Why can't I use git-bisect to find the first *good* commit?
Message-ID: <BANLkTinx1oaqcUSZo-fRAZeHfuoFifVNGQ@mail.gmail.com>
In-Reply-To: <AANLkTinQ0rCw2ydisHra779r6_iSOxqRwOStpJrNbx7h@mail.gmail.com>

On Mon, Mar 28, 2011 at 09:32, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
> But instead I have to do:
>
>    $ git bisect start
>    $ git bisect bad
>    $ git bisect good HEAD~100
>
> And then proceed to mark good revisions as bad, and bad revisions as
> good.
>
> That works, but it's very confusing.
>

To me, at least, that seems perfectly reasonable.

In particular, the problem seems to be your own thinking:

> And then proceed to mark good revisions as bad, and bad revisions as
> good.

Don't think of it like that.