Greg Stein wrote:
>
> On Sat, Sep 28, 2002 at 10:56:15PM -0700, Blair Zajac wrote:
> > Ben Gollmer wrote:
> >...
> > > If you set up per-project mailing lists like I did, it's easy to use the
> > > provided post-commit scripts to send mail on each commit if you have seperate
> > > repos's for each project.
> > >
> > > If you've got multiple projects within one repository and want each one to
> > > have it's own mailing list, be prepared for some script hacking.
> >
> > Not true. The supplied commit-email.pl script takes an optional regular
> > expression command line argument which specifies which commits go to
> > which email addresses.
> >
> > For example, in my repos, I have this in the post commit script:
> >
> > # Send an email out showing the differences in this commit.
> > "$REPOS/hooks/commit-email.pl" "$REPOS" "$REV" \
> > -m '^(branches|tags|trunk)/orca' orca-checkins@orcaware.com \
> > -m '.*' blair@orcaware.com &
> >
> > See the commit-email.pl usage info for more info.
>
> Passing all that stuff on the command line doesn't scale very well, so I'm
> hoping to improve the situation with my mailer.py script (and remove some of
> the inefficiencies of commit-email.pl).
How is mailer.py going to perform the same partitioning of a repos into
multiple mailing lists?
As long as mailer.py can do what commit-email.pl does, I'll be happy.
Best,
Blair
--
Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 30 18:12:50 2002