[16:16] <LeoNerd> Can anyone tell me how to actually drive  bzr bisect  ?
[16:16] <LeoNerd> In all the times I've ever used it it has never worked how I expect
[16:16] <LeoNerd> I'm at -r183. I type  bzr bisect start; bzr bisect no.   (because my bug is absent)
[16:16] <LeoNerd> This automatically moves me to -r189, which is latest.  I type  bzr bisect yes  (beacuse my bug is now present)
[16:17] <LeoNerd> it now says no further bisect is possible.. which Ifind hard to believe - why hasn't it gone to 186 in the middle?
[16:17] <LeoNerd> OK, so maybe my sense of "yes" vs "no" is backwards. lets reset and try again
[16:18] <LeoNerd> So I bisect reset; go back to 183; bisect start; bisect yes.   Now it jumps me right the way back to 94
[16:19] <LeoNerd> Oh, .. OK actually that way round if I do things in the right order it's OK
[16:19] <LeoNerd> I would have expected I can just do any two revisions, either first, and have either one claim "no" vs "yes", and bzr will work it out
[16:21] <LeoNerd> Oh and also  bzr bisect log  crashes:  brz: ERROR: TypeError: write() argument must be str, not bytes