Michiel Holtkamp wrote:
> For mailer question, see below.
> On Nov 11, 2008, at 16:01 , Daniel Shahaf wrote:
>> I'm not wearing my PM hat in this thread. The place to ask is the list,
>> so CCing them, maybe they'll know the answer to your question.
> Whoops, I missed that.
> Ok list, does anyone have an answer to the following question?
> I'm using commit-email.pl for my project (http://supermind.nl/submin/)
> sousers can configure themselves if they want to receive email for every
> commit. It seems that mailer.py is not able to send emails without
> specifying alle the emails in the config-file. To write a specific
> config-file each commit (or check if users changed their settings since
> the last commit) seems a bit bothersome and error-prone to me.
> Is there a better solution, other than using commit-email.pl
> (deprecated) or mailer.py (only email addresses in config file)?
The traditional solution for this is to setup an opt-in mailing list (Google
Group, YaHoo! Group, etc.) for commit emails, to which your mailer script
always transmits, but to which only folks that care are unsubscribed. Does
that not work in your situation?
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2008-11-11 20:23:38 CET