Re: [PATCH v3 0/3] automatically skip away from broken commits

From: Christian Couder <christian.couder@gmail.com>
Date: Jun 9, 2009, 12:26 UTC
Message-ID: <c07716ae0906090526i714bb6c9g4e3d8cf61021af77@mail.gmail.com>
In-Reply-To: <c07716ae0906082124n4a5bfe88md80ba8076c928b76@mail.gmail.com>

On Tue, Jun 9, 2009 at 6:24 AM, Christian Couder<christian.couder@gmail.com> wrote:

>
> So I would be ok to implement a config option or a switch to "git
> bisect start" to let people use a PRNG instead of my algorithm but I
> think something like my algorithm should be the default.

Another reason to have 2 algorithms is that when you use "git bisect run" you might want to use the PRNG one because:

- you don't care much if the bisection use some more steps (as long as
it does not get stuck)
- you can't do much if it get stuck

On the other hand, when you bisect manually:

- you probably won't like it if you are asked to test some commits
that won't give a lot of information
- if it get stuck, you can manually use "git bisect visualize" and/or
"git bisect skip <range>" and/or some other manual commands to do
something about it

Regards, Christian.