Artifact cbc796537d4c9d288c98dbe6a62da42a5243b8c23b4fc3b963e0bc194c3a55c1:

• File .cvs/.old_cvsroot/verifymsg — part of check-in [224423c6a4] at 2021-03-02 08:41:16 on branch master — Move .old_cvsroot and .old_mttroot_cvsroot ⟶ .cvs (user: trnsz@pobox.com, size: 1026) [annotate] [blame] [check-ins using] [more...]
• Executable file .cvs/.old_mttroot_cvsroot/verifymsg — part of check-in [224423c6a4] at 2021-03-02 08:41:16 on branch master — Move .old_cvsroot and .old_mttroot_cvsroot ⟶ .cvs (user: trnsz@pobox.com, size: 1026) [annotate] [blame] [check-ins using]
• File .old_cvsroot/verifymsg — part of check-in [af3953deae] at 2021-03-01 11:39:42 on branch master — Cleanup repository after cvs2git conversion. (user: jeff@gridfinity.com, size: 1026) [annotate] [blame] [check-ins using]
• Executable file .old_mttroot_cvsroot/verifymsg — part of check-in [af3953deae] at 2021-03-01 11:39:42 on branch master — Cleanup repository after cvs2git conversion. (user: jeff@gridfinity.com, size: 1026) [annotate] [blame] [check-ins using]
• File CVSROOT/verifymsg — part of check-in [5e5b873f6f] at 2000-09-15 23:24:16 on branch origin/master — initial checkin (user: gawthrop@users.sourceforge.net, size: 1026) [annotate] [blame] [check-ins using]
• Executable file mttroot/CVSROOT/verifymsg — part of check-in [fe68102f7d] at 2000-12-27 14:14:48 on branch origin/master — initial checkin (user: gawthrop@users.sourceforge.net, size: 1026) [annotate] [blame] [check-ins using]

# 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.