Re: How to keep developers separate from committers?

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jean-Christian Imbeault <address@hidden> writes:

> > 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!

This issue has been raised multiple times in the info-cvs mailing list.
You may find review of the list useful.

For an example of one of the threads, follow this link:

  http://mail.gnu.org/archive/html/info-cvs/2002-05/msg00149.html

There have also been proposed patches to allow for changes in how the
commitinfo trigger is called such that the branch information is
included for each file. See

  http://mail.gnu.org/archive/html/info-cvs/2004-01/msg00024.html

for more information if you are willing to consider patching your cvs
sources with Claus Henriksen's suggested patch.

        Enjoy!
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFA2oWz3x41pRYZE/gRAorNAJwPZkSuDJbN0hCCIQ9i+POBe7osuQCeICHm
4NGk55qfMDZDN30C/npmOS4=
=7J3W
-----END PGP SIGNATURE-----