3 ms·
I’ve always found the git bisect “interface” tedious to use so I do it with a gedit window just writing down how many commits back I jump to etc. Probably the m
by xt00 3y ago
I’ve always found the git bisect “interface” tedious to use so I do it with a gedit window just writing down how many commits back I jump to etc. Probably the most annoying bisecting is when you have to apply patches to a source tree at each point you bisect as well.. but this guy putting building the Linux kernel running it and testing a thing inside his bisect loop automatically is super slick.
- _flux 3y agoI 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.