From: David Brown <david@westcontrol.com>
To: gcc@gcc.gnu.org
Subject: Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?
Date: Tue, 6 Jun 2023 17:37:45 +0200 [thread overview]
Message-ID: <u5njs9$ab7$1@ciao.gmane.io> (raw)
In-Reply-To: <386a1d9c18eb7af15eef409c36a196ec0f99ad22.camel@mad-scientist.net>
On 06/06/2023 14:53, Paul Smith wrote:
> On Tue, 2023-06-06 at 16:36 +0800, Julian Waters via Gcc wrote:
>> Sorry for my outburst, to the rest of this list. I can no longer stay
>> silent and watch these little shits bully people who are too kind to
>> fire back with the same kind of venom in their words.
>
> Many of us have had Dave in our killfiles for a long time already. I
> recommend you (and everyone else) do the same. You won't miss out on
> any information of any use to anyone: he apparently just enjoys making
> other people angry.
>
> I'm quite serious: it's so not worth the mental energy to even read his
> messages, much less to reply to him. Arguing with "people who are
> wrong on the internet" can be cathartic but this is not arguing, it's
> just stabbing yourself in the eye with a pencil. Don't play.
>
If a poster is causing enough aggravation that a large number of people
have killfiled him, is there a process for banning him from the list?
That is surely a better solution than having many people individually
killfiling him? I would assume those with the power to blacklist
addresses from the mailing list do not do so lightly, and that there is
a procedure for it.
David
next prev parent reply other threads:[~2023-06-06 15:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:36 Julian Waters
2023-06-06 12:53 ` Paul Smith
2023-06-06 15:37 ` David Brown [this message]
2023-06-06 17:39 ` David Edelsohn
2023-06-06 18:43 ` Arsen Arsenović
2023-06-08 11:36 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2023-06-05 12:55 Julian Waters
2023-06-05 10:17 Stefan Kanthak
2023-06-05 10:33 ` Jonathan Wakely
2023-06-05 11:35 ` Gabriel Ravier
2023-06-05 22:23 ` Dave Blanchard
2023-06-05 23:59 ` Gabriel Ravier
2023-06-06 0:09 ` Dave Blanchard
2023-06-06 0:28 ` Gabriel Ravier
2023-06-06 0:28 ` Paul Koning
2023-06-06 7:57 ` Jonathan Wakely
2023-06-06 8:31 ` David Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='u5njs9$ab7$1@ciao.gmane.io' \
--to=david@westcontrol.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).