Re: Why can't I use git-bisect to find the first *good* commit?

[Michael Witten <mfwitten@xxxxxxxxx>]

On Mon, Mar 28, 2011 at 09:32, Ãvar ArnfjÃrà Bjarmason <avarab@xxxxxxxxx> 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.
--
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