On 21 August 2015 at 12:25, Richard Biener wrote: > On Fri, Aug 21, 2015 at 12:52 PM, Jonathan Wakely <jwakely....@gmail.com> > wrote: >> On 21 August 2015 at 09:26, Richard Biener wrote: >>> >>> 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. >> >> I'm pretty sure you can have bad older than good, just not when you're >> using git bisect run to automate it. > > The point was to use git bisect.
I assume you mean git bisect *run*, because otherwise what I said stands :-) You can use 'git bisect good' and 'git bisect bad' in any order.
