I take it that your system somehow allows for altering the invocation
of the commit-email.pl script? As each user wants to receive email,
they simply throw themselves onto the command line?
This would seem to imply that the hook script which invokes
commit-email gets rewritten each time somebody wants to receive an
email. It seems that you could have a simple mailer.conf per
repository, a constant hook script, and your system just rewrites the
.conf to append/remove people from the to_addr list. Would that work
in your situation?
[looking at mailer.py and commit-email stuffs today]
Cheers,
-g
On Tue, Nov 11, 2008 at 08:12, Michiel Holtkamp <michiel_at_elfstone.nl> 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)?
>
> Thanks in advance,
> Michiel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: dev-help_at_subversion.tigris.org
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1040899
Received on 2009-01-21 12:27:57 CET