On Tue, Mar 05, 2013 at 05:54:39PM +0100, Lluís Batlle i Rossell wrote: > On Tue, Mar 05, 2013 at 11:48:13AM -0500, Richard Hipp wrote: > > On Tue, Mar 5, 2013 at 11:44 AM, Lluís Batlle i Rossell > > <vi...@viric.name>wrote: > > > > > Hello, > > > > > > fossil bisect currently only allows 'good' or 'bad'. Looking for the > > > introduction of a bug requires also the state of "can't test", because a > > > checkin > > > could be so broken that doesn't allow determining if the checkin is 'good' > > > or > > > 'bad'. > > > > > > Could that 3rd state be introduced? Git allows it easily, for example. > > > > > > > What does bisect do when you give it a "can't test"? > > Suggest another version to test, and keep on going.
Look for 'skip' in git-bisect(1). I think that explains better my idea. Notice that there is a 'git bisect run' error code that the program can return, to indicate 'skip'. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
