view CVSROOT/verifymsg @ 293:315812516608

Changes to the key press handling, if the character is zero check the virtual key code. The virtual key code parameter will always be valid. Also print the character in hex so it can be seen in the test program.
author bsmith@81767d24-ef19-dc11-ae90-00e081727c95
date Tue, 25 Mar 2003 23:44:57 +0000
parents ce3ec30c0d4c
children
line wrap: on
line source

# The "verifymsg" file is used to allow verification of logging
# information.  It works best when a template (as specified in the
# rcsinfo file) is provided for the logging procedure.  Given a
# template with locations for, a bug-id number, a list of people who
# reviewed the code before it can be checked in, and an external
# process to catalog the differences that were code reviewed, the
# following test can be applied to the code:
#
#   Making sure that the entered bug-id number is correct.
#   Validating that the code that was reviewed is indeed the code being
#       checked in (using the bug-id number or a seperate review
#       number to identify this particular code set.).
#
# If any of the above test failed, then the commit would be aborted.
#
# Actions such as mailing a copy of the report to each reviewer are
# better handled by an entry in the loginfo file.
#
# One thing that should be noted is the the ALL keyword is not
# supported.  There can be only one entry that matches a given
# repository.