A "-f" option on rm and mv might do the trick. Default behavior doesn't change. Add two characters to force the filesystem action.
On Wed, Dec 21, 2011 at 3:07 PM, Dmitry Chestnykh <dmi...@codingrobots.com>wrote: > On Wed, 21 Dec 2011 16:52:54 -0500 Jeremy Cowgar wrote: > > > fossil rm should not remove a file it doesn't manage or has changes, > > just like other SCM systems. In this case, the file in question has > > changes, as it is brand new, the entire file has changed. Thus, if > > you were to (in the future) do: > > > > $ fossil rm #document_manager.php# > > File has changes, not removing from disk. > > Exactly. > > Mercurial behavior is a bit different -- it doesn't > remove it because the file has been marked for adding: > > ~ $ mkdir hg > ~ $ cd hg > ~/hg $ hg init > ~/hg $ touch file.txt extra.txt > ~/hg $ ls > extra.txt file.txt > ~/hg $ hg add file.txt extra.txt > ~/hg $ hg rm extra.txt > not removing extra.txt: file has been marked for add (use -f to force > removal) > > -- > Dmitry Chestnykh > http://www.codingrobots.com > _______________________________________________ > 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
