On Tue, Nov 20, 2012 at 8:32 AM, j. van den hoff <veedeeh...@googlemail.com>wrote:
> I already stumbled a couple of times over the fact that `fossil rm' and > `fossil mv' only act > on the repository but not on the check out, i.e. I always have to issue > two commands > in order to actually remove a file from the (future of) the project. > > obviously this is different from other VCSs but I'm missing the point why > it is a good idea > to decouple both actions (removal from tracking and actual removal). > > any enlightenment appreciated... > > right now I'd say it'd be better to keep the actions coupled. > CVS did not couple the actions, and I copied CVS in this regard. I agree with you now, that coupling them is the right thing to do. But I fear to change it because that might cause problems for existing scripts. > > j. > > > -- > Using Opera's revolutionary email client: http://www.opera.com/mail/ > ______________________________**_________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.**org <fossil-users@lists.fossil-scm.org> > http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-users<http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> > -- 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
