Jakub Narębski [off-list ref] writes:
Isn't `--reachable-commits` the same as existing `--ancestry-path`
option to `git log` and friends (I wonder if passing log options to
bisect, that is: `git bisect --ancestry-path ...` would work)?
Yes, I somehow missed it, but you are absolutely correct to point
out that what is being requested is --ancestry-path.
My gut feeling is that by default the command should be taught to
follow the ancestry path, but I say this with reservation, as I am
not sure offhand what it means to traverse along the ancestry path
when there are multiple good commits.
Thanks.