CVSMailer

Author: Bo Berglund

http://w1.862.telia.com/~u86216121/cvsmailer/CVSMailer.html

Text below is from CVSMailer site.

Automatic email on commits and other events

There is often a need to let developers have some form of notification when changes are done to their repository. This can be done in CVS in several ways, one of which is automatic email transmissions on commits and other events. The mechanism that controls this in CVS is the script files in the CVSROOT admin folder. These script files are called whenever CVS performs certain actions and what happens is depending on what is written in the script files. By default the script files are commented out and so contain no actions. There are many different methods of activation out there most of them descending from UNIX and using Perl scripting. I never got that to work probably because I cannot read or write Perl... So I decided to take a different approach and wrote a mailer program myself that handles the email stuff for me. This is the CVSMailer program that can be downloaded here:

Features of CVSMailer

This is a list of some of the features of the program as per version 1.3.1:

Functional features:

• Sends email notification for CVS operations commit, tag and watch

• Now consolidates info from multiple submodules into a single email. Only sends one email for each user operation.

• Handles the new CVSNT taginfo data. No more errors when tagging deep modules.

• Can authenticate with secure mailservers.

• Subject of email configurable.

• Possible to set mail recipients on CVSMailer commandline.

• Recipient list can be hidden in the emails, uses Bcc: field

• Possible to block email to the committer

• Format of mail messages include tabular view of files.

• Repository Prefix can be suppressed from the email message

• Message shows branch tag for each file committed

Troubleshooting features:

• More logging for debug, can be switched to quiet or silent mode for production

• Can be set to save email message to a test file instead of sending the email

• Can be set to keep temp files for inspection

• Can't have the diff IN the mail. People aren't going to click through.