From owner-freebsd-hackers Tue Jun 11 01:46:35 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA14490 for hackers-outgoing; Tue, 11 Jun 1996 01:46:35 -0700 (PDT) Received: from DATAPLEX.NET (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA14480 for ; Tue, 11 Jun 1996 01:46:29 -0700 (PDT) Received: from 199.183.109.242 by DATAPLEX.NET with SMTP (MailShare 1.0fc5); Tue, 11 Jun 1996 03:46:20 -0600 Message-ID: Date: 11 Jun 1996 03:46:05 -0500 From: "Richard Wackerbarth" Subject: Multiple Mailing lists To: "hackers@freebsd.org" , "Jonathan M. Bresler" X-Mailer: Mail*Link PT/Internet 1.6.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jonathan Bresler writes: >> There are 8 lists. > in this example. there are about 51 FreeBSD mailing lists. If you could read, you would notice that I acknowledged that there were other lists. However, many of them are not a problem. I doubt there there is much cross posting to ctm-src-2_1 and something else :-) If we handle the "most common offenses" we will have solved 99% of the problem. I suspect that most people could live with the rest. > stable, current, hackers, questions...thats 16 already. ugh > i aint real excited about setting up 32 lists (5 done already) Only if you offer all the combinations. Actually, I don't see a real problem having even 128 lists if we automate the signup process so that it is transparent. The individual lists are just (the equivalent of) alias records used for distribution. A fairly simple Perl (or other language) script can compute the code number of the resulting list that is appropriate for individual additions or deletions from each of the named lists. -- Richard Wackerbarth rkw@dataplex.net -- ...computers in the future may have only 1,000 vacuum tubes and weigh only 1/2 tons. -- Popular Mechanics, March 1949