From: "Arsen Arsenović" <arsen@aarsen.me>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: David Brown <david@westcontrol.com>, gcc@gcc.gnu.org
Subject: Re: Will GCC eventually learn to use BSR or even TZCNT on AMD/Intel processors?
Date: Tue, 06 Jun 2023 20:43:05 +0200 [thread overview]
Message-ID: <86ttvk3006.fsf@aarsen.me> (raw)
In-Reply-To: <CAGWvnyk49_CG0spdQ0i80rnnDUw9yxTaUwE2LYEZXYJfO7pZ6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
David Edelsohn <dje.gcc@gmail.com> writes:
> The GNU Toolchain leadership has blacklisted people in the past, but we
> have used the power sparingly.
>
> The behavior of the individual attracts attention, albeit negative, while
> not effectively accomplishing what he purports to desire. The recommended
> solution is to ignore the poster instead of trying to encourage him to
> communicate more effectively.
IMO, the sparing usage of this power on what are clearly purely abusive
participants can only drive away users and contributors. It seems
reasonable to establish a process for dealing with incidents like this
(and appeals, of course), especially given their frecency.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next prev parent reply other threads:[~2023-06-06 18:43 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
2023-06-06 17:39 ` David Edelsohn
2023-06-06 18:43 ` Arsen Arsenović [this message]
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=86ttvk3006.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=david@westcontrol.com \
--cc=dje.gcc@gmail.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).