RE: How to keep developers separate from committers?

[Jean-Christian Imbeault]

> From: address@hidden [mailto:address@hidden On Behalf Of 
> 
> Your sysadmin is mistaken.
> 
> The commitinfo trigger is able to run
> 
>     cvs -Qn status
> on the list of files and determine the 'Sticky Tag:' line that relates
> to the file being committed.

I don't know much about cvs administration but I can't see how commitinfo
applies in this case. I will look more into it, Also I would like to help my
sysadmin learn more, if you have any links/pointers on where we can learn
more about this and how he (the sysadmin) can use this method for
controlling read/write (i.e. commit) access to branches please let me know?
(I had a quick look at the O'reilly book but can't find anything appropriate
just now)
 
> Use branches.

That would definitely make everything easy. I just need to find out more
about restricting access. Hopefully reading up on commitinfo will point me
in the right direction!

Thanks,

Jc