Richard Biener <richard.guent...@gmail.com> writes: > Btw, I've done this once now and it kind of works. You need to write your > tests in a way to support gits limited way of searching (the past has to be > always good, the future bad) - I've tried to find a change that was _fixing_ > a problem, something that doesn't seem to be supported. Heh. Well, > just "fixed" the test script.
You can surely bisect a fix, you just have to remember that bad means fixed and good means unfixed. And of course, the git community is working on enhancing the bisect UI for this use case. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."