On Sat, May 21, 2011 at 4:29 PM, Gour-Gadadhara Dasa <g...@atmarama.net> wrote: > On Sat, 21 May 2011 14:32:34 -0400 > Richard Hipp <d...@sqlite.org> wrote: >> Does anybody have any other suggestions on how to prevent the lose >> of uncommitted work? > > Maybe not suggestion to prevent losing of uncommitted work, but I'm > thinking about using 'stash' in such situation.
Doing a fossil update should never delete uncommitted changed files. Zed's post implies this happened. That said. I routinely backup my projects so I am far less likely to loose more than a day's work. This is not a matter of not trusting a given VCS, whether Fossil, git, some expensive commercial VCS or any other, it is simply a matter of prudence. Better to have multiple backup systems as this helps mitigate the effects of failures in any one system. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
