Re: Persistent Notification Emails

[Ricardo Cortes]

Actually, we already have commented out the DEFAULT definition in the
loginfo file and we are sending notifications based on the CVS module
name.  I removed the problematic CVS module from the loginfo file but,
unfortunately, we are still receiving emails from this project.  I
believe this is happening because the new project was imported from an
existing project and that existing project is still listed in the
loginfo file.  Hope that makes sense.

On Wed, 2005-03-16 at 12:18 -0500, Todd Denniston wrote:
> Ricardo Cortes wrote:
> > 
> > Hi,
> > 
> > We divided one of our projects up awhile ago into two separate projects,
> > one for static content and one for dynamic Java/JSP files.  When we
> > initially created the static content project, we performed an import so
> > we wouldn't lose the CVS history.  After doing this we realized that we
> > no longer cared to receive CVS commit notifications on the new static
> > content project.  I tried modifying the loginfo file (we are using the
> > mailAndLog.sh script with logInfo.pl) and removing the entry for the new
> > static content project but we are still getting inundated with unwanted
> > emails from the new static content project.  Does anyone know how to
> > stop these emails from being sent out for just our static content
> > project?  Any help would be greatly appreciated as I wasn't able to find
> > an answer on Google nor in the archives.
> > 
> > Thanks!
> > Ricardo
> check "$CVSROOT/CVSROOT/loginfo", I suspect you will find the only
> un-commented line is something like:
> DEFAULT ...logInfo.pl...
> 
> if you change "DEFAULT" (or perhaps they change the syntax to ALL) to the
> name of the module(s) where you still want email, then you will only get
> email on those modules.
> See the manual here:
> https://www.cvshome.org/docs/manual/cvs-1.11.19/cvs_18.html#SEC173
>