Return to verifymsg CVS log

Up to [CSRG BSD Unix] / CVSROOT

Annotation of CVSROOT/verifymsg, revision 1.1

1.1     ! root        1: # The "verifymsg" file is used to allow verification of logging
        !             2: # information.  It works best when a template (as specified in the
        !             3: # rcsinfo file) is provided for the logging procedure.  Given a
        !             4: # template with locations for, a bug-id number, a list of people who
        !             5: # reviewed the code before it can be checked in, and an external
        !             6: # process to catalog the differences that were code reviewed, the
        !             7: # following test can be applied to the code:
        !             8: #
        !             9: #   Making sure that the entered bug-id number is correct.
        !            10: #   Validating that the code that was reviewed is indeed the code being
        !            11: #       checked in (using the bug-id number or a separate review
        !            12: #       number to identify this particular code set.).
        !            13: #
        !            14: # If any of the above test failed, then the commit would be aborted.
        !            15: #
        !            16: # Format strings present in the filter will be replaced as follows:
        !            17: #    %c = canonical name of the command being executed
        !            18: #    %I = unique (randomly generated) commit ID
        !            19: #    %R = the name of the referrer, if any, otherwise the value NONE
        !            20: #    %p = path relative to repository
        !            21: #    %r = repository (path portion of $CVSROOT)
        !            22: #    %l = name of log file to be verified.
        !            23: #
        !            24: # If no format strings are present in the filter, a default " %l" will
        !            25: # be appended to the filter, but this usage is deprecated.
        !            26: #
        !            27: # Actions such as mailing a copy of the report to each reviewer are
        !            28: # better handled by an entry in the loginfo file.
        !            29: #
        !            30: # One thing that should be noted is the the ALL keyword is not
        !            31: # supported.  There can be only one entry that matches a given
        !            32: # repository.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.