Stephan Beal <[email protected]> wrote: > On Wed, Dec 9, 2009 at 10:09 PM, Jeremy Cowgar <[email protected]> wrote: > > > I'd like to see the option be defaulted to on and then for that one in a > > million time when you don't actually want to remove the file, you can > > override it via the command line. > > > > i would recommend the flag name --keep for that. >
Yes, that's good, however, what about for mv ? I guess --keep would work as well and if you mv with a --keep, then it turns into a copy, as far as the file system is concerned. > 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. > > :-? > Yes. I am sure that we can do a check such as the one when calling revert. In this case it could be: "remove file 'abc.txt'? this file has changed since last commit [yN]?" So, the chances of loss go down further. Now, if no changes were made, then obviously no message would appear. We would then also have to provide a --force to both the mv and rm options so that a rm/mv could be scripted (not get the prompt). Jeremy _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
