In article <3ogck7$j5a@belfort.daimi.aau.dk> shakti@daimi.aau.dk
(Claus L{gel Rasmussen) writes:

|> While I am tended against moderation of comp.std.c++, my irritaion over
|> these irrelevant postings to this group is steadily increasing, and I
|> must say, that I would probably vote YES to such a proposal.

My basic instinct is against moderation, too.  But I suspect that JF
is just a starter.  As the net grows, so does the proportion of people
on it who have no respect for others.  Note the recent thread
concerning the exploitation of GNAT by its authors.

The only group I've seen that has been spared this sort of noise is
comp.compilers.  By a curious co-incidence, it is also the only
monitored group I read.

|> Perhaps we could reduce the proposed moderation policy to something like:
|> everything is accepted except those ravings from our *dear* fellow here.

I agree with the proposition: when in doubt, let it through.  From
their postings, I gather that this is more or less the opinion of the
proposed monitors.  (I might add that there are some of the more
recent postings by JF that I would have passed, were I a monitor.
Perhaps if this group is monitored, he will clean up his act enough so
that most of his postings get through.  If so, we might even
eventually learn something about c+   .  Shucks, some of us might even
try using it:-).)
--
James Kanze         Tel.: (+33) 88 14 49 00        email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs-Bourgeois, F-67000 Strasbourg, France
Conseils en informatique industrielle --
                              -- Beratung in industrieller Datenverarbeitung

Thus spake scherrey@proteus-tech.com:

>Folks -

> FWIW, I've got a certain individual in my kill file and have, since this
>addition, been able to concentrate more on relevant C++ standards issues
>much better. However, I still have to wade through a tremendous number of
>replies to this person's postings so it's still having an impact. How about we
>all just refrain from responding to such posts all-togather and, I might suggest
>that you build a kill file of your own so the temptation will no longer be there
>to reply.


I would strongly support this.

I'm in the exactly same situation. My newsreader (nn) is not capable of
killing replies to postings from the person in question.

While I am tended against moderation of comp.std.c++, my irritaion over
these irrelevant postings to this group is steadily increasing, and I
must say, that I would probably vote YES to such a proposal.

Perhaps we could reduce the proposed moderation policy to something like:
everything is accepted except those ravings from our *dear* fellow here.

--
Claus L. Rasmussen email: shakti@daimi.aau.dk
Knudrisgade 14 B II voice: +45 86 18 42 65
8000 Aarhus C
Denmark

scherrey@proteus-tech.com writes:
> FWIW, I've got a certain individual in my kill file ...
>However, I still have to wade through a tremendous number of
>replies to this person's postings so it's still having an impact.

If you are using rn or one of its descendants, try the following pattern
in your kill file:

/News1.mcs.com/h:j

This will kill all replies to that certain person, as well as replies
to replies, except from those folks who are using newsreaders that don't
do References headers correctly.
--
-- Joe Buck  <jbuck@synopsys.com> (not speaking for Synopsys, Inc)
Phone: +1 415 694 1729

Folks -

 FWIW, I've got a certain individual in my kill file and have, since this
addition, been able to concentrate more on relevant C++ standards issues
much better. However, I still have to wade through a tremendous number of
replies to this person's postings so it's still having an impact. How about we
all just refrain from responding to such posts all-togather and, I might suggest
that you build a kill file of your own so the temptation will no longer be there
to reply.

     thanx much & later,

 Ben Scherrey
 Proteus Technologies, Inc.

>>>>> scherrey  <scherrey@proteus-tech.com> writes:

>  FWIW, I've got a certain individual in my kill file and have, since
> this addition, been able to concentrate more on relevant C++ standards
> issues much better. However, I still have to wade through a tremendous
> number of replies to this person's postings so it's still having an
> impact. How about we all just refrain from responding to such posts
> all-togather and, I might suggest that you build a kill file of your own
> so the temptation will no longer be there to reply.

If you also kill messages with News1.mcs.com in the References field, you
can avoid replies as well.  I do this, so the only messages I see regarding
that individual are ones (like yours) that start a separate thread.

Jason