Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!tut.cis.ohio-state.edu!navajo.cis.ohio-state.edu!martens
From: martens@navajo.cis.ohio-state.edu (Jeff Martens)
Newsgroups: news.groups
Subject: Re: CALL FOR DISCUSSION comp.sys.alliant
Message-ID: <76213@tut.cis.ohio-state.edu>
Date: 26 Jan 90 04:41:41 GMT
References: <6828@hacgate.scg.hac.com> <WEENING.90Jan16202020@Gang-of-Four.Stanford.EDU>
Sender: news@tut.cis.ohio-state.edu
Reply-To: Jeff Martens <martens@cis.ohio-state.edu>
Distribution: usa
Organization: Ohio State University Computer and Information Science
Lines: 17

In article <WEENING.90Jan16202020@Gang-of-Four.Stanford.EDU> weening@Gang-of-Four.Stanford.EDU (Joe Weening) writes:

>I'm in favor of comp.sys.alliant, but I think that it shouldn't be
>limited to the FX series (there will be other Alliant systems in the

	[ ... ]

Do it.  I don't think the original call for votes said anything about
limiting it to the FX, but I agree that this would be a mistake.  

Would the charter of comp.sys.alliant allow the discussion of FX-based
systems, like Cedar?  I guess this is a moot point if the group's
unmoderated, but that'd be a point in its favor.
-=-
-- Jeff (martens@cis.ohio-state.edu)

My program to detect infinite loops seems to be stuck in a loop...