From: "Jakub Narębski" <jnareb@xxxxxxxxx>
W dniu 20.02.2017 o 21:31, Alex Hoffman pisze:
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.
isn't that spelt `--ancestry-path` ?
(--ancestry-path has it's own issues such as needing an --first-parent-show
option, but that's possibly a by the by)
--
Philip