On Jan 9, 2014, at 21:38 , Remigiusz Modrzejewski wrote: >> [*] The fact that Fossil is a DVCS doesn't ease my mind on this matter. All >> that means is that if there ever is a data loss, it will take some time to >> propagate among the copies, during which time I *may* catch it in time to >> recover, before the last copy gets tainted. > > The fact that Fossil is sort of write-only should.
What I meant is obviously append-only. > By design Fossil does not allow changing (thus destroying) any historical > records. > The only unwanted thing that can conceivably propagate is your CC number in a > test file. > If you are concerned by new software errors eating your code, simply don't > update your central location. > Fossil can easily interoperate in the distance of many versions. > > Kind regards, > Remigiusz Modrzejewski _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
