Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!usenet.ins.cwru.edu!cwjcc!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery)
Newsgroups: news.groups
Subject: Re: Splitting Comp.Sys.Mac again (was Re: Too many messages in ....)
Message-ID: <1990Feb10.004016.9052@NCoast.ORG>
Date: 10 Feb 90 00:40:16 GMT
References: <629@ascom.UUCP> <38387@apple.Apple.COM> <1603@umigw.MIAMI.EDU> <38392@apple.Apple.COM> <552@dino.cs.iastate.edu>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery)
Followup-To: news.groups
Organization: North Coast Public Access UN*X, Cleveland, OH
Lines: 26

As quoted from <552@dino.cs.iastate.edu> by mehl@cs.iastate.edu (Mark M Mehl):
+---------------
| I posted a followup to this article nearly two days ago, but I guess
| the news software must of ate it.  Here we go again.
| 
| chuq@Apple.COM (Chuq Von Rospach) writes:
| >My preferences right now would be:
| >comp.sys.mac.misc
| >comp.sys.mac.d
| >comp.sys.mac.wanted
| >comp.sys.mac.futures
| 
| Well, let me conservatively suggest:
| comp.sys.mac.app   (for discussing Mac application programs)
| comp.sys.mac.os    (for discussing operating sys and networking)
+---------------

Unless it's all leakage/misposting from comp.protocols.appletalk, I suggest a
newsgroup for network issues; not everyone uses or even needs AppleTalk.  If
such issues belong in c.p.a, then that group is probably misnamed; it looks
like a group for discussing AppleTalk standards, not AppleTalk implementation.

++Brandon
-- 
Brandon S. Allbery    allbery@NCoast.ORG, BALLBERY (MCI Mail), ALLBERY (Delphi)
      uunet!cwjcc.cwru.edu!ncoast!allbery ncoast!allbery@cwjcc.cwru.edu