On 4/14/2016 11:10 AM, Stephan Beal wrote:
On Thu, Apr 14, 2016 at 7:00 PM, Warren Young <w...@etr-usa.com
<mailto:w...@etr-usa.com>> wrote:
    On Apr 12, 2016, at 11:30 PM, Stephan Beal <sgb...@googlemail.com
    <mailto: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. :)
....

    The ability to bisect is one of the strongest arguments in favor of
    version control.

I've needed it in the past, but as luck had it only on projects from before I knew about fossil, and I suspect before fossil really existed. CVS was fine for keeping a change log and record of the past from which with great luck and careful usage one *might* be able to return to a past build. Bisect was not something that would have been easily done with it.

Since I've been using fossil, luck has mostly kept me from needing to search for obscure bugs that were latent until noticed. But from watching the list and noticing the ease with which others have used it for that purpose, it was clearly not only a compelling argument in favor of version control, but also a compelling reason to never check in anything to trunk that breaks the build.

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.)

I'm 100% with Stephan on this one. On those rare occasions where I've wanted the effect of fossil clean, I've opened a fresh working directory instead.

<<Insert rant here about IDEs that insist on storing full path names to their internal implementation and installed tools as well as to the user's source and object files. The biggest offenders are the customized junk provided by SOC vendors without which it is often impossible to build their sample code or even cross compile for their platform without a whole lot of reverse engineering of their tool chain.>>

--
Ross Berteig                               r...@cheshireeng.com
Cheshire Engineering Corp.           http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to