Path: utzoo!attcan!uunet!cs.utexas.edu!uwm.edu!rpi!sci.ccny.cuny.edu!dan From: dan@sci.ccny.cuny.edu (Dan Schlitt) Newsgroups: news.admin Subject: Re: rmgroup comp.sys.masscomp Message-ID: <1990Feb20.145934.1918@sci.ccny.cuny.edu> Date: 20 Feb 90 14:59:34 GMT References: <161@gazette.bcm.tmc.edu> <1990Feb9.174809.15759@vicom.com> <169@gaz Organization: City College of New York - Science Computing Facility Lines: 24 In article lear@turbo.bio.net (Eliot) writes: :I'd like to second one of Michael Berch's comments about this whole :affair. I believe the most important use of news.announce.newgroups :is to announce configuration changes such as the ones that Stan made. :news.announce.newgroups has a nice low volume, so that news :administrators (among others) can see what's happening in the :hierarchies without having to wade through the cruft in news.groups. :Of course, this presupposes that people will send me those changes. :-- :Eliot Lear :[lear@TURBO.BIO.NET] Absolutely! I do group changes by hand. I don't want random messages from off-site changing my active file. A message in news.announce.newgroups would have explained things to my satisfaction. Even an explaination in the control message would have done the job. But why the multiple control messages? If one doesn't do the job why expect that three will do it better. -- Dan Schlitt Manager, Science Division Computer Facility dan@sci.ccny.cuny.edu City College of New York dan@ccnysci.uucp New York, NY 10031 dan@ccnysci.bitnet (212)690-6868