> "RA" == Russ Allbery <[EMAIL PROTECTED]> writes:
RA> Instead, what about a temporary freeze when each list is created? Give it
RA> a day or two after it's created before it will accept traffic; have the
RA> traffic be held for that long while people subscribe. Would that help
RA>
Johan Vromans writes:
> Currently, when a new sublist is announced, it takes some time to get
> subscribed (usually my first 3 or 4 attempts fail since the list does
> not exist yet) and when I wait a while and the subscription succeeds,
> I already have missed several messages.
I think the best
Johan Vromans <[EMAIL PROTECTED]> writes:
> I would plea for autosubscribing perl6-language list members to every
> sublist that gets spawned. The reason is continuity.
Currently, I'm trying to deal with the volume of Perl lists by subscribing
to just the "top-level" lists and relying on the pro
Johan Vromans wrote:
> An alternative solution is to automatically sent all messages that have
> been posted to the sublist so far, upon subscription.
If there are less than 100 of them, this is probably an excellant idea.
I still haven't received anything directly from -mlc, although I've
rece
Original Message
Subject: Re: Sublist auto*
Date: Sat, 05 Aug 2000 14:39:33 -0400
From: Edwin Wiles <[EMAIL PROTECTED]>
Organization: Totally Disorganized
To: Johan Vromans <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Johan Vromans wrote:
> I would plea for autosubscribing perl6-language list members to every
> sublist that gets spawned. The reason is continuity.
Yes, I strongly agree with this! Especially since I'm subscribed from
two different addresses and now chair two lists. I really like it if the
discussion wouldn't start w
