Re: Read only access to cvs

[Steve deRosier]

Purushotham Komaravolu wrote:
Hi,
 I am new to CVS administration.I need help in seting up the following.
1) Read only access to repository:
Developers ger read/write 
access but QA and others get read-only access.
As an alternative, give developers real access to the repository with 
full read/write access, but install ViewCVS and only give the QA/others 
access to that.  If they only need to take a look at the code on 
occasion with no need to edit, why give them actual CVS access at all? 
Also, the deveopers will find that ViewCVS is handy anyway.

- Steve



___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Re: Read only access to cvs

[Larry Jones]

Purushotham Komaravolu writes:
> 
> This is a multi-part message in MIME format.

Please do not send MIME and/or HTML encrypted messages to the list.
Plain text only, PLEASE!

>  I am new to CVS administration.I need help in seting up the
> following.
> 1) Read only access to repository: 
> Developers ger read/write
> access but QA and others get read-only access.
> 2) Multiple teams sharing different modules:
>   We have multiple teams working on multiple modules.  Each
> teammember can access his/her teams module in RW(read/write) mode, where
> as he/she can access other team's module in read only fashion.



> PS: is it recommended to have individual repositories for each project??

Not usually.

-Larry Jones

It's no fun to play games with a poor sport. -- Calvin


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Read only access to cvs

[Purushotham Komaravolu]

Hi,
 I am new to CVS 
administration.I need help in seting up the following.
1) Read only access to repository: 
        
                
                
    Developers ger read/write access but QA and others get 
read-only access.
2) Multiple teams sharing different 
modules:
  
We have multiple teams working on multiple modules.  Each teammember can 
access his/her teams module in RW(read/write) mode, where as he/she can access 
other team's module in read only fashion. PS:   is it recommended to 
have individual repositories for each project??
 
Can somebody advice me on how to setup/administer 
the following scenario in a manageable fashion.
Thanks
Regards,
Puru 
 
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs