> long long long time ago Fossil destroyed code for Zed Shaw 1) No, it didn't. Please read the part of the thread after Zed's initial panic attack. 2) To the

> long long long time ago Fossil destroyed code for Zed Shaw 1) No, it didn't. Please read the part of the thread after Zed's initial panic attack. 2) To the best of our[1] knowledge, fossil itself has never caused a single byte of data loss. When fossil checks in new data, it reads that data back (in the same SQL transaction the data was written in) to ensure than it can read what it wrote with 100% fidelity, so it's nearly impossible to get corrupted data into fossil without going into the db and massaging it by hand. People have lost data by storing their only copy of a repository on failing/failed storage or on a network drive, but no software can protect against hardware failure and nobody in their right mind tries to maintain an active sqlite db over a network drive (plenty of people do it, despite the repeated warnings of anyone who knows anything about sqlite, and they have only themselves to blame when it goes pear shaped). Fossil makes syncing to/from a remote copy absolutely trivial, so any failure to regularly sync copies to a backup is end-user error. [1] = the fossil developers.