[cvsnt] FW: CVSNT / CVSMailer Consolidation Question

Iwan java at i-ware.net
Tue May 13 22:32:44 BST 2003


Hmmm, any other way to get around this? I would really like to have the
functionality of consolidating commits over quite some time, say 4 hours.
Such that people are either waiting for changes and updating themselves, or
are notified twice a day.

Alternatively, maybe it is possible to subscribe per module to be notified?

Iwan.


> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org 
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Kai Bernhard
> Sent: dinsdag 13 mei 2003 17:53
> To: cvsnt at cvsnt.org
> Subject: Re: [cvsnt] FW: CVSNT / CVSMailer Consolidation Question
> 
> 
> Iwan wrote:
> 
> >>This is was my assumption of the functionality is:
> >>
> >>[You setup CVSMailer such that it delays for an x amount of 
> seconds, 
> >>say 600 (10 minutes). Now every commit that is performed in 
> these 10 
> >>minutes is consolidated into one email send out, this to 
> prevent the 
> >>subscribers of being flooded by emails.]
> >>
> >>Now either I am wrong, or I've done something wrong in setting up 
> >>CVSMailer, since I get an email for every commit I've performed 
> >>instead of a consolidated email for all commits performed 
> within that 
> >>timeframe.
> >>    
> >>
> AFAIK, CVSMailer will only consolidate messages of ONE USER 
> OPERATION - that means every commit or tag you perform will 
> result in JUST ONE EMAIL. That is what a user would normally 
> expect, but is not 'CVS Standard' because one user operation 
> may result in multiple cvs operations (e.g. one for each 
> subdirectory). So it's not a configuration problem but just 
> the way it is. Bo will correct me if I'm wrong.
>  
>  
> Kai Bernhard
> 
> 
> 
> 
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
> 




More information about the cvsnt mailing list