On Nov 12, 2008, at 4:23 , C. Michael Pilato wrote:
> 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?
It's a good option if your repositories don't change much, that's for
sure.
In my case, I want a flexible environment where you can create a
repository for a short period of time with a couple of persons. For
example, I use it to collaborate with fellow students, one repository
for each course, seperate permissions (because of different group
members) and seperate mailing notifications. I'm just too lazy to
setup a new mailinglist for each project and I'm making submin for
people who are just as lazy as I am :)
Also, I want all configuration in one spot, so you don't have to login
to different systems. That's the whole idea of submin: easy
configuration, spending as little time at configuring the repositories
and more time in the actual development of your projects.
Thanks for the input though, if there are no more suggestions, I think
I'll just keep on using the (soon to be deprecated) commit-email.pl
and later on try to make it work for mailer.py.
Regards,
Michiel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-12 07:12:18 CET