On Thu, Jul 27, 2000 at 06:58:51AM -0400, Michael G Schwern wrote: > Problem. You have to be a procmail wizard to get anything done. There's this article in this month's TPJ... :) > Maybe I'm a Luditte, but I've never learned mail filtering, and having > this knowledge as a prerequisite for contributing to Perl might be a > silly barrier to others as well. Yes, this is one reason I consider multiple lists to be a barrier to entry. > Alternative. Have one big list made up of smaller lists. In essense, > multiple views of the same data. For example. I subscribe to > perl6-qa@perl.org. All posts to that list go to p6p (our big mailing > list) as well as perl6-qa. All replies to that post on p6p are > mirrored on perl6-qa. There are many ways to implement this which are > largely irrelevant the moent. Right. Now I post a new thread to p6p. Where does it go? Would you have to be reading p6p to see it? But we're hypothesising a bunch of people only reading the subgroups, which would make sense because they don't want to read a big mailing list. So those of us who only want to read a big mailing list get shut out. Or we have to work out where to forward the new thread, which is what the big list was trying to avoid in the first place. Sorry, perl6-all doesn't work. -- The PROPER way to handle HTML postings is to cancel the article, then hire a hitman to kill the poster, his wife and kids, and fuck his dog and smash his computer into little bits. Anything more is just extremism. - Paul Tomblin, in the monastery.Thread Previous | Thread Next