Re: Git bisect does not find commit introducing the bug

From: Jakub Narębski <jnareb@gmail.com>
Date: Feb 20, 2017, 20:35 UTC
Message-ID: <ca1ef8f6-58cf-4994-d1bf-39e04b42dd4c@gmail.com>
In-Reply-To: <CAMX8fZUNHmouUsgEY3+0CmTaEp+y5b1-Cp8Nk3OttTc30v0R5A@mail.gmail.com>

W dniu 20.02.2017 o 21:31, Alex Hoffman pisze:

Show 9 quoted lines

> I see two different problems each with a different assumption (see the
> definition of "bisectable" in the email of Junio C Hamano):
> 
> 1. (Current) Assume the entire history graph is bisectable. DO: Search
> where in the entire graph the first 'trait'/transition occurs.
>
> 2. (New) Assume only the graph between one good commit and one bad
> commit is bisectable. DO: Search where the first transition occurs in
> the graph between these two commits.

If `git bisect` is/would be affected by `git log` history-related options then this is what `--strict-ancestor` option gives/would give.

-- 
Jakub Narębski