I would suggest taking a look at:
http://linuxdevcenter.com/pub/a/linux/2003/06/05/scripts.html
This requires some scripting on your part. Our script queries our bug
tracking system (ClearQuest) and validates that the bugid is valid and that
the bug is in the correct state (Code Review) and that
Thanks Scott，The method you provided seems doing pre-commit review. But now we
have changed our idea. We want do automation on post-commit review. Thus, If
somebody has commmited his code, a CVS post-commit script will be stimulated
and post a review request for this user. Now the key problem
We are doing reviews prior to the changes being commited to CVS.
To enforce this process, you can modify the CVS pre-commit script. This
script can then check change for review approval.
We currently require the bugid to be in the cvs commit log, as such we query
the bug tracking system and
