On Dec 17, 2009, at 3:29 PM, Wilson, Ronald wrote: > Also, while inspecting the code, I noticed > that yesRevert is not initialized at the top of the loop, so there > could > be unexpected results for multiple files. See my c++ style comments > below.
I was working on that earlier today. Maybe I messed something up. While out running just now, it occurred to me that we really ought to get rid of the --yes switch on "revert" all together and just make it do the revert without confirmation. But also make "revert" undoable, so if you accidently revert some work that you really wanted to keep, you can just "fossil undo" to get it back. D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
