Xref: utzoo news.admin:10604 news.groups:23719 comp.unix.internals:244
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!uw-beaver!ubc-cs!alberta!oha!tony
From: tony@oha.UUCP (Tony Olekshy)
Newsgroups: news.admin,news.groups,comp.unix.internals
Subject: Re: c.u.wizards vs. c.u.internals
Message-ID: <450@oha.UUCP>
Date: 12 Sep 90 19:56:14 GMT
References: <34639@eerie.acsu.Buffalo.EDU> <18530@rpp386.cactus.org> <3370@stl.stc.co.uk> <1857@van-bc.wimsey.bc.ca>
Organization: Olekshy Hoover & Associates Ltd., Edmonton, Alberta, Canada.
Lines: 22
In-Reply-To: Message <1857@van-bc.wimsey.bc.ca> dated 11 Sep 90 21:18:06 GMT

In message <1857@van-bc.wimsey.bc.ca>, sl@van-bc.wimsey.bc.ca (Stuart Lynne)
writes:
>
> Until another vote is called on this subject van-bc will carry
> comp.unix.internals without removing or aliasing comp.unix.wizards.

That's just what I'm doing here.  Maybe because of the harsh lessons from
the climate up here, we Canadians have learned not to tear down bridges until
the new ones are proven.

I think the smart thing to do at this time is to undo the c.u.w rmgroup and
let this thing ride for the rest of the year.  It's just possible that the
new c.u.* groups will soak up much of the stuff that was overloading c.u.w. 
Internals is a valid but separate topic from wizards anyway.  Can't I be
a unix wizard on an externals topic?

On the other hand, we could try c.u.necromancer ;-).

--
Yours etc., Tony Olekshy.               Internet: tony%oha@CS.UAlberta.CA
					  BITNET: tony%oha.uucp@UALTAMTS.BITNET
					    uucp: alberta!oha!tony