Xref: utzoo comp.lang.c++:10756 gnu.g++.help:245
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!samsung!sol.ctr.columbia.edu!lll-winken!unixhub!shelby!mcnc!thorin!homer!leech
From: leech@homer.cs.unc.edu (Jonathan Leech)
Newsgroups: comp.lang.c++,gnu.g++.help
Subject: Re: Anyone for decoupling GNU and c.l.c++?
Message-ID: <18070@thorin.cs.unc.edu>
Date: 12 Dec 90 00:37:22 GMT
References: <59548@microsoft.UUCP> <9012051730.AA14088@teacake.Eng.Sun.COM> <DAVIS.90Dec6145442@barbes.ilog.fr> <MULLER.90Dec7112929@molecule.src.umd.edu>
Sender: news@thorin.cs.unc.edu
Reply-To: leech@homer.cs.unc.edu (Jonathan Leech)
Organization: University Of North Carolina, Chapel Hill
Lines: 20
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

In article <MULLER.90Dec7112929@molecule.src.umd.edu> muller@src.umd.edu (Christophe Muller) writes:
>Comme on guys ! Give us a break with this story now..
>
>If you don't want to read the messages that appear in gnu.g++, DON'T READ
>THEM!
>
>What about:
>
>	(gnus-kill "Newsgroups" "gnu\\.g++\\.help")

    What a good idea.  Let's follow up on it by merging all newsgroups
and using kill mechanisms to select what to read.

    Until we can do that, how about the much simpler mechanism of
keeping FSF political posturing out of comp.lang.c++ by disconnecting
the groups.
--
    Jon Leech (leech@cs.unc.edu)    __@/
    "Opossums ran amok in Chapel Hill this weekend..."
	_The Daily Tar Heel_, 11/1/88