Marc MERLIN <[EMAIL PROTECTED]> writes:
>> Perhaps an -option would be better than special-casing a list name.
> I thought about it, but it breaks the option parsing a bit since
> remove_members kind of expects a list name.
How about an argument that tells the program to interpret the list name
a
Hi everybody,
I just produced the patch included below. It allows to configure not to
add the List-* header lines to outgoing non-digest messages. I needed this
to hide the HTTP URLs for the webinterface, as Mailman is used "just" as
the mailing list backend and the webinterface is to be used by
On Wed, Apr 04, 2001 at 11:11:54PM +0200, [EMAIL PROTECTED] wrote:
> Note that the patch adds a new attribute to the MailList object. This
> usually breaks existing mailing lists.
That comment troubles me. Isn't the point of object oriented design
pretty precisely to avoid the need for such comm
> "JRA" == Jay R Ashworth <[EMAIL PROTECTED]> writes:
JRA> That comment troubles me. Isn't the point of object oriented
JRA> design pretty precisely to avoid the need for such comments?
The issue here is that in essence the patch is changing the schema for
the list configuration da
On Wed, Apr 04, 2001 at 07:32:58PM -0400, Barry A. Warsaw wrote:
> JRA> That comment troubles me. Isn't the point of object oriented
> JRA> design pretty precisely to avoid the need for such comments?
>
> The issue here is that in essence the patch is changing the schema for
> the list c
> "JRA" == Jay R Ashworth <[EMAIL PROTECTED]> writes:
JRA> You're saying that a list object *wraps* a database, then.
JRA> If so, yeah, the object sure as hell *ought* to deal with
JRA> that issue itself.
JRA> Careful how you use the word "databases"... I *think* you
JRA
On Wed, Apr 04, 2001 at 08:19:35PM -0400, Barry A. Warsaw wrote:
> JRA> You're saying that a list object *wraps* a database, then.
> JRA> If so, yeah, the object sure as hell *ought* to deal with
> JRA> that issue itself.
>
> JRA> Careful how you use the word "databases"... I *thi
On Wed, 4 Apr 2001 19:17:12 -0400
Jay R Ashworth <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 04, 2001 at 11:11:54PM +0200, [EMAIL PROTECTED] wrote:
>> Note that the patch adds a new attribute to the MailList
>> object. This usually breaks existing mailing lists.
> That comment troubles me. Isn't
> "JRA" == Jay R Ashworth <[EMAIL PROTECTED]> writes:
JRA> Ah. The problem comes from the fact that the exported
JRA> marshals won't have the new data. Perhaps python needs to
JRA> evaluate something else for it's marshalling file format?
JRA> XML? H??
I'm not sure h
Hi everybody,
Having read the replies for my previous patch so far, I have produced
version 2 of it.
I would also like to note that the functionality applies to both regular
and digest messages anyway, so one of the comments from my last posts
should be treated as nonsense.
Due to this, I have
On Wed, Apr 04, 2001 at 10:17:07PM -0400, Barry A. Warsaw wrote:
> JRA> Ah. The problem comes from the fact that the exported
> JRA> marshals won't have the new data. Perhaps python needs to
> JRA> evaluate something else for it's marshalling file format?
>
> JRA> XML? H??
11 matches
Mail list logo
