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.
j.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
