Terri Oda writes:
Not very. Not only is it tightly integrated, but any text change
will have to go through all the many translators for various
languages.
Aha. You beat me to that one.
I think that one way to deal with that, though, would be to simply
refactor the existing
--On 19 June 2008 13:21:31 -0400 Terri Oda [EMAIL PROTECTED] wrote:
I think we could benefit a fair bit from having a simple and an
expert interface for the list administrators. I had a number of
replies both on and off list saying yes! please! so I take it I'm not
the only one who thinks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 19, 2008, at 5:36 PM, Barry Warsaw wrote:
If you have a specific hardship with our adoption of GPLv3 for
Mailman 2.2 and 3.0, please let me know. I may not be able to
answer your questions, but we can bring in some official GNU and FSF
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everybody,
I get asked all the time: will you set up my lists for pay?
I'm not interested or able to do this kind of work, but I always feel
bad about turning people away without some pointers to other people.
I've started a wiki page for
Oh yeah!!! I did that one a while ago!
Bob
-- Original Message ---
From: Fil [EMAIL PROTECTED]
To: Mailman Developers mailman-developers@python.org
Sent: Fri, 20 Jun 2008 19:48:14 +0200
Subject: [Mailman-Developers] better logging of undiscernable bounces
A very useful patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 20, 2008, at 1:48 PM, Fil wrote:
A very useful patch (against 2.1.11rc1)
--- Mailman/Queue/BounceRunner.save.py 2008-06-20
19:34:51.0 +0200
+++ Mailman/Queue/BounceRunner.py 2008-06-20
19:35:44.0 +0200
@@ -230,7
Mark Sapiro writes:
discernable addresses' message, so the list name isn't really required
since the list will be identifiable with the first change, and it may
even seem redundant, but I think it's more consistent to include it on
all the messages.
+1
+1
Consistency and (some)
