[cvsnt] Re: Emailing Summary of Commits

Bo Berglund bo.berglund at telia.com
Wed Apr 16 05:41:59 BST 2003

On Wed, 16 Apr 2003 16:17:30 +1200, "Deck" <d at d.com> wrote:

>Right now, we are receiving emails for every commits
>on our CVS. We need to be notified what modules
>have been affected,what are the changes and who
>made the changes. And that's a lot of emails as we
>commit quite often. Reading all of them can be quite
>tedious so we don't bother reading them anymore
>sometimes. Is there anyway we can just receive an
>email with the summary of commits for the day based
>on modules and the description of changes?
>thanks in advance

You have to write your own handler for this (goes into the loginfo or
postcommit scripts).
Basically you need to collect the data for each commit somewhere and
then periodically (once a day) compile it all ito something that can
be sent out. Note that each invocation of a cvs command from the
client can result in several triggers on the script level so you have
to look out for this too.

In my CVSMailer program I collect the data for a single user command
into a temp folder and then after some delay I send it all out as an
email. This reduces the amount of emails sent for multiple folder
commits to one.
What you want to do is more ambitious and you need to think it out
properly before doing it.

(Bo Berglund, developer in Sweden)

More information about the cvsnt mailing list