I think the interface is actually quite nice! When I need to analyze bisect results myself in such a situation, I usually just do it like (cd src; patch < nee

I think the interface is actually quite nice! When I need to analyze bisect results myself in such a situation, I usually just do it like (cd src; patch < needed_patches && make && do_the_test; git reset --hard) git bisect good (or bad or skip it patches failed to apply) and repeat those from my command line history as needed. I think it works out fine. Git bisect can also dig inside merges, which I think would be a bit more annoying with just a list of commits.