Comment 2 for bug 1051395

Not exactly :-(. I implemented bug 683822 yesterday in lp:~naesten/bzr-bisect/683822-bisect-start-range-argument , and now when I try to use the feature for a real bisection I discover that it uses the opposite convention from "bisect run"!

I think it would be much simpler to keep straight if we just called them "bad" and "good", and never mind if the meanings sometimes have to be reversed to get the desired results...