Re: How to keep developers separate from committers?

[Mark D. Baushke]

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

Todd Denniston <address@hidden> writes:

> "Mark D. Baushke" wrote:
> > Of course, the point I was trying to make in that thread was that it is
> > POSSIBLE to do the same thing without any of the patches to cvs being
> > necessary.
> > 
> Mark,
> would  cvs_acls[1] in the source tarball, or cvs_acls2[2] be more direct
> pointers to what he wants, with out having to patch CVS?

Yes. 

> [1] cvs-1.11.16/contrib/cvs_acls.in 
> [2][sorry only had the tarball from 1.11.16 available so I don't know if
> cvs_acls2 has been merged later.]

cvs-1.11.17/contrib/cvs_acls.in is the same file as the 1.11.16 version
and this is also the same version as the cvs-1.12.9/contrib/cvs_acls.in
version.

> http://lists.gnu.org/archive/html/info-cvs/2004-03/msg00401.html
> http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=cvs_acls2&idxname=info-cvs&max=20&result=normal&sort=score

Yes, those are good pointers.

My recollection is that Peter Connolly was going to clean up a few more
warnings in his version of cvs_acls2.in as well as provide an option to
use an old-style CVSROOT/cvsacl file if it is found. When he does that,
his version of the file will be committed to replace the older
cvs_acls.in file.

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

iD8DBQFA2v7L3x41pRYZE/gRAmDjAJ9oiitQ9rlT/f4J2TlLzlxM9M63JgCeKHED
lPcfBY4WhyAYbGcuLg2hvpY=
=G49J
-----END PGP SIGNATURE-----