From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.5-pre1 Date: 17 Dec 92 19:33:15 GMT From: saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!sdd.hp.com!hpscit.sc.h p.com!icon.rose.hp.com!tom@ames.arc.nasa.gov (Thomas Vachuska) Subject: Re: Lets split comp.lang.ada into multiple groups to confine flames Message-ID: List-Id: Alex Blakemore (alex@cs.umd.edu) wrote: : make comp.lang.ada obsolete and create a small set of groups instead. : : some suggestions : : comp.lang.advocacy - for the flame wars : comp.lang.programmer - for discussions of design/development Ada language issues : (or comp.lang.technical or better name?) : comp.lang.announce - moderated, low volume important announcements : of meetings, products, standards, new mandates :) etc : comp.lang.misc - catch all : Am I wrong if I assume that you really meant to write 'comp.lang.ada.*' instead of 'comp.lang.*'? At least for the *programmer, *announce, and *misc groups anyway. IMHO, there should really be only one 'comp.lang.*.advocacy' group. Kind of a /dev/null... huh? ;-) I'll vote YES on comp.lang.advocacy, comp.lang.ada.[programmer, announce, misc] . Thomas Vachuska ------------------------------------------------------------------------------ tom@mothra.rose.hp.com (916)-785-4983 (Telnet & Voice Mail) ------------------------------------------------------------------------------