Hi, Barry Warsaw wrote:
> On Fri, 2005-07-01 at 20:04, Mark Sapiro wrote: > > >>2). I'm not a Mailman developer, and I can't speak for anyone's intent, >>but a patch which makes the above conditional on a new list attribute, >>updates Mailman/Gui/ContentFilter.py to maintain and document the new >>attribute and updates Mailman/MailList.py to set the default value >>(current behavior) for new and migrated lists, might be accepted. > > > Definitely. I don't remember exactly why we ended up with this behavior > unconditionally, but I agree now that it probably should be optional. > > Care to work out a patch? > Anyone done this already? I'm going to do this as a part of my lecture (Anatomy of Mailman) for our MS course students tommorow. :-) -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
