Thanks for the reference Mark! The latest script (March 24) is located in the enhancement bug:
https://ccvs.cvshome.org/issues/show_bug.cgi?id=170 pc > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Mark D. Baushke > Sent: Friday, September 10, 2004 3:13 PM > To: Fernando Silveira > Cc: [EMAIL PROTECTED] > Subject: Re: disabling branch commit > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Fernando Silveira <[EMAIL PROTECTED]> writes: > > > Dear list, > > > > I work for a software development company and we use CVS > to control > > our source code. Right now I am trying to make my CVS > server to disable > > commits to a specific BRANCH (or TAG) of a module. > > > > I've studied and tryied it a lot of times using "commitinfo", > > "loginfo" and other configuration files but I had no > success. It seems > > that I cannot have the information of which revision, tag or branch > > before committing to block it, but I'm not sure. I wonder > if you could > > help me with this problem, have any tips, docs or anything > that helps or > > tells if it is possible or not. > > > > Thanks in advance. > > The list has talked about branch locking and access control > on multiple > occasions. > > The following link points to a reasonable cvs_acls2 script: > > http://lists.gnu.org/archive/html/cvs-utils/2004-02/msg00047.html > > that allows you the control you wish. > > -- Mark > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.3 (FreeBSD) > > iD8DBQFBQib03x41pRYZE/gRAoHnAJ9/NnL1/QoOp0BKAk4EKQ8vgYZ1vACghD4m > ZrebyJyihK5QCAvauXxp67c= > =0rrA > -----END PGP SIGNATURE----- > > > _______________________________________________ > Info-cvs mailing list > [EMAIL PROTECTED] > http://lists.gnu.org/mailman/listinfo/info-cvs > _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
