On Jul 4, 2018, at 9:50 AM, Dewey Hylton <dewey.hyl...@gmail.com> wrote: > > The solution ended up being much less messy than I anticipated
Yes; while Fossil will let you create awful messes, this is mitigated by several design choices: 1. It’s really hard to make Fossil actually lose data. It can be done, but it takes enough effort that you’re highly unlikely to do it by accident. 2. If you have a mess with no data loss, recovery within the existing repository is usually simple enough that restoring from a backup copy and replaying your work is almost never the best option. 3. Once bitten this way, the reason why you were bitten and the right way to avoid it is usually clear. Contrast <cough> other systems where you can be told how you screwed up and how to fix it and still be at risk of doing it again because the right way doesn’t “click”. > This is a great community. Fossil is worth fighting for. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
