Pedro Henrique Ponchio writes:
>
> I just need to know how to prevent the group B to write over the code of
> the group A, but allows then to checkout the modules builded by group A,
> see the files, etc. There is any way to keep the group B away from
> change the group A modules??
Set the protections on the repository directories so that group B has
read permission but not write permission. Since users need to be able
to create lock files even for reading, you'll have to use LockDir= in
CVSROOT/config to put the lock files somewhere that everyone has write
permission.
-Larry Jones
I must have been delirious from having so much fun. -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
