On Wed, 2009-12-09 at 22:22 +0100, Stephan Beal wrote: > That said, presumably when you "rm" a file, it already exists in the > repo, and the chance of a significant loss due to an unwanted unlink() > on the file seems to be small.
But the function that the current method provides is one that's really needed sometimes. I.e., "don't keep track of this file anymore". I like that that's convenient, too. So, for what little it's worth, I'd like fossil mv and fossil rm to really perform the file system operations by default, and let me access the current behavior with the --keep flag. If that's not acceptable, let them keep their current default function, but add a --do or --force flag to make them work on the filesystem, too. I agree with Jeremy's proposal to prompt before destroying work that hasn't been committed (and the consequent necessity of the --force option). -- Joshua Paine LetterBlock: Web applications built with joy http://letterblock.com/ 301-576-1920 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
