I completely agree to change current mv/rm commands so as they perform the OS level operation too. It looks like an inconsistency that they do not move/remove the file in the local repository and they move/remove it in the cloned repositories.
If some script breaks, it can be repaired. No problem. RR 2015-03-03 23:12 GMT+01:00 bch <brad.har...@gmail.com>: > Something like a cmv, crm (these are off the top of my head, don't > dwell on the poor names) command that is "complete mv", and "complete > rm" would fit the bill, where it appropriately wraps the current mv/rm > commands is feasible, though. > > -bch > > > On 3/3/15, Richard Hipp <d...@sqlite.org> wrote: >> On 3/3/15, to...@acm.org <to...@acm.org> wrote: >>> You could always have a global setting on how to deal with this (old way >>> vs >>> new way) to keep everyone happy :) >>> >> >> So nobody would ever know what the "mv" and "rm" commands actually do >> without first consulting their settings. No. I think that is a very >> bad solution. >> >> -- >> 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 >> > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
