Fossil – Simple, high-reliability, distributed software configuration management

Re:Fossil – Simple, high-reliability, distributed software c... by e98cuenc on Thursday December 04, 2014 @01:26AM (#8698093)

I would have done exactly the same thing. He is using a SCM that deleted all its files due to a bug. He tried to recover its deleted files, and it seems the next commands utterly killed any hope of recovery. What was him supposed to do? keep in its mind perfectly the internal state of Fossil after an unknown bug to find which command, if any, could recover its files? I would have panicked, tried every command I could think of and started crying.

After Fossil deleted its files he informs the maintainer of the bug, giving a clear description of what happened, and decides to switch to a more mainstream SCM.

I don't get why you're giving him so much heat. He seems to me constructive (the bug was fixed) and mature (he went to a more mainstream SCM that is less likely to have some kind of "never seen before" bug while you just "make a branch").

[ Parent | on HN ]

Re:Fossil – Simple, high-reliability, distributed software c... by tedunangst on Thursday December 04, 2014 @01:59AM (#8698174)

For next time:

    cd ..
    cp -R wrkdir backup
    cd wrkdir
    fossil dickitup

[ Parent | on HN ]

Re:Fossil – Simple, high-reliability, distributed software c... by Dewie on Thursday December 04, 2014 @07:38AM (#8698944)

> What was him supposed to do?

Use some automated backup tool that had nothing to do with fossil.

[ Parent | on HN ]