*I* can accept Larry's opinions if there are ways to limit the import operation to only some specific persons, say, the PM and the
main developer.
Why would you want to do that? There's nothing you can do with import that you can't do with add, commit, tag, etc.
It really sounds a strange question. And it is not only I that want this feature. However, I'll try to name some reasons:
1) To avoid misuse. I once encountered a developer just trying to use cvs and importing an existing module. As CVS administrator I do not like it at all. Of course he should not do it, but it is better to prevent it for ever than to educate everyone, esp. when I am not his boss.
2) To restrict the creation of modules (and initial files therein). Maybe I am ignorant, but import is the only way I know to create modules on the CVS server. And I am sure none of my colleagues knows of yet another way. I never know how to use "cvs add" to do that as you implied. Nor have I read any CVS books about it.
Best regards,
Wu Yongwei
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
