Next: rcsinfo, Previous: Trigger Scripts, Up: Administrative files [Contents][Index]
There are three kinds of trigger scripts (see Trigger Scripts) that can be run at various times during a commit. They are specified in files in the repository, as described below. The following table summarizes the file names and the purpose of the corresponding programs.
The program is responsible for checking that the commit is allowed. If it exits with a non-zero exit status the commit will be aborted.
The specified program is used to evaluate the log message, and possibly verify that it contains all required fields. This is most useful in combination with the rcsinfo file, which can hold a log message template (see rcsinfo).
The specified program is used to edit the log message, and possibly verify that it contains all required fields. This is most useful in combination with the rcsinfo file, which can hold a log message template (see rcsinfo). (obsolete)
The specified program is called when the commit is complete. It receives the log message and some additional information and can store the log message in a file, or mail it to appropriate persons, or maybe post it to a local newsgroup, or… Your imagination is the limit!
• commitinfo: | Pre-commit checking | |
• verifymsg: | How are log messages evaluated? | |
• editinfo: | Specifying how log messages are created (obsolete) | |
• loginfo: | Where should log messages be sent? |
Next: rcsinfo, Previous: Trigger Scripts, Up: Administrative files [Contents][Index]