On Sat, May 21, 2011 at 11:55 AM, Zed A. Shaw <zeds...@zedshaw.com> wrote:
> I don't know what the hell has been changing lately, but this is really > starting to piss me off. First I get tons of leaves that won't go away > and that I have to constantly close over and over, and *now* I'm getting > this crap: > > http://dpaste.de/cY4y/ > > I can put up with the stupid leaves behavior, but this is completely > unforgivable. There's no way in hell *anyone* should be able to get > fossil in a state that causes it to REMOVE ALL MY FILES. > (1) "fossil undo" should restore all your files whenever something like this happens. (2) I just checked in a change that prints a "panic" message if Fossil gets into a state where it might want to delete all your files on an update. Still searching for the root cause of the problem.... > > How do I fix this, and more importantly, how is it going to be prevented > in the future? > > And no, nobody on my project actually did this. There's no commit that > removes everything, and in fact fossil itself thinks the files are > missing after the update. > > -- > Zed A. Shaw > http://zedshaw.com/ > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
