On Thu, Apr 14, 2016 at 7:00 PM, Warren Young <w...@etr-usa.com> wrote:
> On Apr 12, 2016, at 11:30 PM, Stephan Beal <sgb...@googlemail.com> wrote: > > > > i haven't ever bisected. > > Wow… > > I don’t bisect every day, but when I do bisect, I bisect with Fossil. :) > i've just been lucky - never needed to use it to find where a particular problem arrived :). (But that's admittedly luck, rather than any form of skill!) > Bisecting is most useful when you get a bug report from the field and > can’t see from that report how any of the recent changes caused the > failure. See, if anyone other that myself used my software, i might have needed it ;). > I used bisect on Fossil itself to find the regression that broke sorting > in the Tickets view, fixed in [0e555dee6]. The problem was introduced > about 6 months prior to the bug’s discovery. How would you have found a > problem like that without bisecting? > i'd have left it to you to find :-D! > I suppose if you’re working on software with 100% regression test coverage, LOL! Nope - just lucky. i was born in Las Vegas - maybe that has something to do with it ;). > The ability to bisect is one of the strongest arguments in favor of > version control. > i admit that it's a fantastic capability, i've just never needed to use it. (Contrast with "fossil clean" - i have Opinions about anyone other than myself cleaning up my source trees, and simply _won't_ use that feature.) -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
