On Mon, 5 Sep 2005, Sonny Rao wrote:
>
> Can this method detect breakages that are spread across more than one
> patch? I suppose it'll just trigger on the last patch commited in the
> set in this case?
It will trigger on just the commit that introduces the user-visible
breakage, so yes, it's usually the last in a series (or the first one, for
that matter).
And it's not perfect. A problem that fades in and out is not something you
can do binary searching on. For example, sometimes a bug gets introduced
and ends up being dependent on things like cache alignment or some
variable layout etc, so you only _see_ the problem occasionally, and it
ends up happening due to totally unrelated changes - then the bisection
algorithm ends up being totally useles..
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
