[cvsnt] RE: Looking for RCSINFO and template examples

[Williams, Tim]

To answer my own question, there is a nice little example here:
	
http://www.einval.com/~steve/software/cvs-bugzilla/#rcsinfo

I get the template just fine, but am having trouble altering the commit
message using verifymsg and the config option RereadLogAfterVerify=yes.
I call my verifymsg.pl Perl script just fine and can allow the commit if
the message meets certain length and content criteria, but I can not
alter/format the message at all.
This may be due to the fact that I am running CVSNT 2.0.4 on the client
end (using TCVS 1.4.5) and 2.0.5 on the repository server.  Upgrading is
currently not an option since we depend on the ability to place
sandboxes on network drives...so I guess I'm stuck for now.

Funny - while researching this issue I found an almost identical
question from me back in Aug 2004. I guess most folks don't use RCSINFO.
I think it has great potential for helping guide/standardize commit
comments.  

Tim


>  -----Original Message-----
> From: 	Williams, Tim  
> Sent:	Thursday, February 24, 2005 9:19 PM
> To:	'cvsnt at cvsnt.org'
> Subject:	Looking for RCSINFO and template examples
> 
> Hi folks,
> 
>   I'm looking for any examples of how to setup commit templates using
> RCSINFO.   I see lots of mention in the documentation that it "can be
> done" , but does anyone have real-life examples of its use?    We
> would like to flag certain commit comments as being relevant to our
> validation efforts, and then be able to extract those comments later.
> Even something as simple as providing a field that could later be
> parsed with Perl, such as:
> 
> QC:  
> 
> That, if filled in as :
> 
> QC: Y
> 
> We would extract that comment using a script called by LOGINFO
> 
> TIA,
> 
> Tim 
> 
> SAS Systems Administrator
> PRA International
> Charlottesville VA, USA
>