Xref: utzoo news.groups:11756 comp.sys.ibm.pc:33655 comp.windows.ms:867 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!ames!ucsd!hub!tangello!erbo From: erbo@tangello.ucsb.edu (Eric J. Bowersox) Newsgroups: news.groups,comp.sys.ibm.pc,comp.windows.ms Subject: Re: CALL for DISCUSSION: comp.sys.os2 Summary: Another name possibility Keywords: OS2, newgroup, discussion , vote, name Message-ID: <2242@hub.UUCP> Date: 24 Aug 89 04:00:52 GMT References: <2194@dlvax2.datlog.co.uk> <1191@tukki.jyu.fi> Sender: news@hub.UUCP Reply-To: erbo@cornu.ucsb.edu (Eric J. Bowersox) Followup-To: news.groups Organization: My Refrigerator is a Sun 3/140 Lines: 28 In article <1191@tukki.jyu.fi> tarvaine@tukki.jyu.fi (Tapani Tarvainen) writes: :In article <2194@dlvax2.datlog.co.uk> mor@datlog.co.uk ( Mike O'Reilly ) writes: :>This is a CALL for DISCUSSION of "comp.sys.os2" and related newsgroups. : :It should be "comp.os.os2". Another name possibility: "comp.sys.ibm.pc.os2". Before anyone whips out the flamethrowers :-), listen to this justification: OS/2 is still pretty much tied down to the IBM PC (or, at least, AT or better) architecture, and may remain that way for quite some time. (Or it may not. We'll see about that.) So, it would make sense to me to put the group on the PC-specific hierarchy. Of course, this will probably invite crossposting, but a lot of stuff is going to get crossposted anyway, I think. Precedent for this exists, namely, "comp.sys.mac.hypercard" and "comp.sys.mac.programmer," subgroups of "comp.sys.mac" which talk about highly specialized subsets of Macintosh issues. "comp.sys.ibm.pc.os2" would follow this trend. Of course, I'm not _opposed_ to "comp.os.os2," I'm just presenting an alter- native for those who may be interested. So what do you think? Like it? Spike it? Do I deserve a Boot to the Head? Or what? | Disclaimer: "Disclaimer?! I don't even KNOW her!!" -- M. Coohill | | * Eric J. Bowersox (ERBO) * LIVE! from Isla Vista, California! | | erbo@cornu.ucsb.edu ...!{ucbvax,ucsd}!ucsbcsl!cornu!erbo | | Brain fried error reading drive C -- Abort, Retry, Ignore, Fail? |