Re: Enhancing mailer.py for email-based issue trackers

Jon Bendtsen wrote: 
> On 20/11/2009, at 12.45, Branko Čibej wrote:
> >> I think this and other patches just fell through.
> >
> > Sorry about that. It doesn't have anything to do with the merit of the
> > idea, or the quality of the patch -- it's just that people are often
> > working on other things, or don't have time, or whatever. Things like
> > that happen on volunteer-based projects.
> 
> i know, and i am not blaming anyone.
> 
> I havent been pushing it as much as i could myself either.

Speaking for myself, mailer.py is one of many categories of dev email
that I don't normally look at, but I still want to see it kept
maintained and useful.

So I had a quick look at this patch. At a quick scan through, it looks
sensibly designed and implemented and has documentation in the
mailer.conf example file. Consider that a vote of confidence.

I am reluctant to commit something I haven't tried out and reviewed, and
can't spend the time on this one, but it looks "safe" in the "do no
harm" and "is a reasonable direction of progress" senses so shall I just
commit it?

Yes, I shall commit it, unless anyone quickly lets me know otherwise.

- Julian

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2425428

Please start new threads on the <[email protected]> mailing list.
To subscribe to the new list, send an empty e-mail to <[email protected]>.