I've attached a Perl script that I wrote to require bug ids in commit
messages on a per-branch basis. Its core is derived from cvs_acls, and
it should be installed in a similar way. No guarantees, and you should
have someone who knows Perl better than I do read it and check it very
carefully before using it.

Server version: cvs 1.12.9

~Matt 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] 
> On Behalf Of vik
> Sent: Tuesday, May 24, 2005 10:20 AM
> To: info-cvs@gnu.org
> Subject: Re: cvs verifying log message format per branch
> 
> Thanks for your quick replies! I dont know perl myself,but am going to
> ask a co-worked to help out. Say my production branch is called
> 'production-release-1-1',  so one way is to checkout verifymsg from
> CVSROOT and then modify it to use
> 
> cvs -qn status | grep '^ 'production-release-1-1' |.
> 
> I did read about the cvs_acls script and am assuming its available in
> the CVSROOT directory by default? I would surely prefer to use it if
> its been tested and used before, given my zero knowledge of
> Perl/scripting tool.
> 
> Thanks again!
> 
> Vik
> 
> _______________________________________________
> Info-cvs mailing list
> Info-cvs@gnu.org
> http://lists.gnu.org/mailman/listinfo/info-cvs
> 

Attachment: require_bugid
Description: require_bugid

_______________________________________________
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs

Reply via email to