On Tue, Jul 26, 2011 at 4:24 PM, Remigiusz Modrzejewski <l...@maxnet.org.pl> wrote: > > About general reliability: I've never encountered any data loss/corruption > with Fossil. This is even when I use my own compiled versions derived from > the trunk at random moments. It's also quite rare to read about any bugs in > the software. I'd say it's built to a pretty good quality, but not yet the > one of sqlite. Also the process is a bit lacking, with the ticket system > being a ghost town (see http://fossil-scm.org/index.html/rptview?rn=2).
Yeah, I guess he was just unlucky and/or a bit careless if it's the fossil revert that actually destroyed his files. I am very trusty of fossiI. I compile it from trunk, I have an automated script that just updates to trunk, recompile fossil and do a full rebuild on all repos that I run pretty much every day. I actually have this running from cron on my home fossil backup server so it autoupdates to the latest trunk revision of fossil every few hours (I also do backups, I'm not that crazy). I have one repository in particular which is rather large (480MB) with a 220MB checkout containing of thousand of files, including some binaries (it might sounds like some serious, large application and/or dataset, but it's actually my world of warcraft addons, configuration files and screenshot directories that I archive and sync between different PCs using fossil) and while this repo exposed some subtle bug in fossil that made it fail to sync properly some time ago it never broke in any serious, data corrupting fashion. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
