Re: enforcing comments when checking in

[Mark D. Baushke]

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

Purushotham Komaravolu <address@hidden> writes:

> Thanks for the prompt answer. Does it work with pserver??

Yes.

> I have attached some test configuration files. Let me know if they r
> correct.

It is hard to determine that out-of-context.

Your verifymsg trigger will invoke the script

  /data/cvs/repository/CVSROOT/templates/test.verify 

if and only if the file being committed is under the top-level 'tc'
module. 

Note: Your script is allowed to modify the log message by default and
does not actually require any change to the CVSROOT/config file.

Your rcsinfo trigger will put a copy of the file
/data/cvs/repository/CVSROOT/templates/test.template into CVS/Template
in the checked out tree of the 'tc' module to use as the template for a
'cvs commit' Note that this may be overridden by a user using either the
options -m 'log-message-string' or '-f logmsg-file' to cvs commit:

     cvs commit -m 'My log message goes here.'
or
     echo 'My log message goes here.' > mylog.txt
     cvs commit -F mylog.txt

The test.template contains four sections: 'Comment:', 'DefectId:',
'UserId:', and 'Reviewer:' 

Note however, that I would suggest that 'UserId:' may be confusing and
should really be provided by the commit itself as a part of the mapping
of your :pserver: userids to real userids. Your :pserver: should be
setting the environment variable CVS_USER for this purpose in your
verifymsg script if you really think you need it in the log message
itself instead of just in the author=userid part of the RCS file for a
particular commit.

I suggest you test your changes on a temporary repository to see if they
do what you expect them to do.

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

iD8DBQE/+aMJ3x41pRYZE/gRAi6XAJoCb89PrV+mBrfQHMmSBoqaoQetowCghh0V
RQ6EJoJUc2C4aLb1LZECJMY=
=u5qw
-----END PGP SIGNATURE-----