What you're describing here is the crux of the problem, and I think can be fairly described as separation of concerns -- the domain of the version control is it's controlled files, and if a file is not handled by version control, (ie: fossil rm somefile), should fossil be reaching outside of its area of responsibility, well-intentioned or not ?
-bch On 3/4/15, Martin Gagnon <eme...@gmail.com> wrote: > On Wed, Mar 04, 2015 at 06:33:07PM +0100, Ramon Ribó wrote: >> I think that both worlds can live together without any problem. >> >> - When doing "fossil mv A B" >> >> * If A exists and B does not exist in file system, rename file A to B >> * If B exists and A does not exist in file system, do nothing >> * If either both exist or none exists, warn and stop > > This make sense to me.. > >> >> - When doing "fossil rm A" >> >> * If A exists in file system, delete file A > This is another story. Sometimes, I just want to remove file from > revision control, but I still want to keep the file on my filesystem. So > for "fossil rm", I would prefer to don't touch the file system by > default. > >> * if A does not exist in file system, do nothing > > <snip> > > Regards, > > -- > Martin G. > _______________________________________________ > 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
