[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: users file and notification

From: Ruud Dozijn
Subject: RE: users file and notification
Date: Mon, 15 Dec 2003 11:07:42 +0100

From: Peter Connolly <address@hidden>
To: "'Ruud Dozijn'" <address@hidden>, "'address@hidden'" <address@hidden>
Subject: RE: users file and notification
Date: Thu, 11 Dec 2003 09:07:53 -0800

> Can anybody tell me if there is a way to tell cvs to let the
> file users map
> cvs users to email adresses? Or if there's another way to
> configure cvs
> to send mail to the cvs users instead of system users?

If you want users notified when commits are made to specific CVS modules, this is done by using the following 'contrib' scripts and control files: is a PERL script that is run after commit processing

loginfo: This is the control file used by log_accum. Each line contains a pattern of the module you are tracking; the email addresses that require notification; and the current $USER.

commit_prep: is a PERL script that will facilitates getting all the commit log messages (and diffs if requested) into a single log_accum email.

commitinfo: has a line for each module to track and the current $USER.

Once you've installed CVS, look in the .../cvs/share/cvs/contrib directory for the scripts.

hi Peter,

thank you for this hint; the scripts are not exactly what I meant, because they send email on commits, not on watch notifications. But I can of course change the mail call in CVSROOT/notify in a self made script call that uses $USER to determine who is interested.

As far as I understood the watch notification mechanism of cvs, the following happens: - to setup the file system authentication properly, users A, B, C and D (working on the same project) have in CVSROOT/passwd the same group G1 (third field in the passwd file)
- user A and B have added a watch on on the edit action of a certain file,
- user C issues a 'cvs edit' on that file
- cvs sees that it is necessary to notify two users: it make two identical notification emails and sends these two emails to the same email address: the email address of user G1; - maybe user A, B, C and D read the email of G1. The first reader determines if the rest ever see the two emails. It is not certain who of them reads it and how recent the notification is when they read it. Or, more likely, G1 is a user account with no home directory and no users that log in. The emails are lost.

If the cvs users of my company find it interesting enough I will make a script that sends email to the addresses associated with cvs users (is this list to post that script?). Still I am wondering why the notification mechanism is designed to know which cvs users need a watch notification, but destroy this information and send mail to an attribute that user share with other users (the system user email account)?
Or am I misunderstanding something???

thanks in advance, Ruud

MSN Search, for accurate results!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]