Skip to content
Snippets Groups Projects
Select Git revision
  • trunk
  • RELEASE_6_5_DRIVEDB
  • RELEASE_6_6_DRIVEDB
  • RELEASE_7_0_DRIVEDB
  • RELEASE_7_2_DRIVEDB
  • RELEASE_7_3_DRIVEDB
  • RELEASE_6_0_DRIVEDB
  • RELEASE_6_1_DRIVEDB
  • RELEASE_6_2_DRIVEDB
  • RELEASE_6_3_DRIVEDB
  • RELEASE_6_4_DRIVEDB
  • tags/RELEASE_7_4
  • tags/RELEASE_7_3
  • RELEASE_5_41_DRIVEDB
  • RELEASE_5_42_DRIVEDB
  • RELEASE_5_43_DRIVEDB
  • tags/RELEASE_7_2
  • tags/RELEASE_7_1
  • tags/RELEASE_7_0
  • RELEASE_5_40_DRIVEDB
20 results

verifymsg

Blame
  • verifymsg 1.00 KiB
    # 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.