-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The cvs-cvs address is for reporting commits to the repository, not questions. I have directed the reply to the [email protected] list.
Jean-Claude Gervais <[EMAIL PROTECTED]> writes: > What is the best way (read that as 'simplest/easiest way') to restrict > access in CVS? For write access, use of the CVS triggers is a good way. There is a script in the contrib directory called cvs_acls you can use. For read access, the use of UNIX groups is reasonable. > For example, if you want to allow only certain users to manipulate > tags/branches. You might want some users to create tags, but not be able > to move them, also you might want to prevent people from inadvertantly > deleting branches. The taginfo CVS trigger may be used to prohibit the modification of tags by individuals. > Is there a friendly way (for example using access rights in CVS/NT) or > must you absolutely write taginfo scripts and such? This list is for CVS, not CVSNT. If you wish to ask about CVSNT, you will find better answers from the http://www.cvsnt.org/ web site. -- Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF5S7NCg7APGsDnFERAjRUAKD5rpE99KKOqpV2eYF/Jf9ZOTDvVQCfa3rI 5Elci3OS3WAzs/vPZskl/UE= =D215 -----END PGP SIGNATURE----- _______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
