On Tue, Mar 05, 2013 at 12:02:21PM -0500, Richard Hipp wrote: > On Tue, Mar 5, 2013 at 11:57 AM, Lluís Batlle i Rossell > <[email protected]>wrote: > > > > > > > > > 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'. > > > > That documentation doesn't really tell me very much. But I'll try to come > up with something. Just not right now as there are several other issues on > other projects that need to take priority, and you can easily work around > this by typing "fossil up next" or "fossil up prev" when you hit an > untestable check-in.
oh perfect. I didn't know this. Thank you! (btw, remember that annotate is broken :) _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
