From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: overseers@gcc.gnu.org, Jeff Law <law@redhat.com>,
Richard Biener <rguenther@suse.de>
Subject: Re: Please lock bug report 92729 or ban abebeos@lazaridis.com from Bugzilla
Date: Fri, 14 May 2021 01:05:54 +0200 [thread overview]
Message-ID: <2c7a5314-d481-c61b-be8f-8b12aed42dfb@physik.fu-berlin.de> (raw)
In-Reply-To: <20210513225447.GH10366@gate.crashing.org>
Hi Segher!
On 5/14/21 12:54 AM, Segher Boessenkool wrote:
>> The person is now attacking me personally on the bugtracker:
>>
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729#c61
>>
>> Would it be possible to take some action now? I it would be great if his off-topic,
>> defamatory comments could be deleted from this bug report. None of the claims this person
>> is making are valid and it's not okay that a bug tracker is used to attack me personally.
>
> I tagged the comment as "spam" (and as "abuse" and as "admin" but we do
> not seem to implement those) so at least it is hidden by default now.
Thanks. That already helps a lot. Maybe flag the ones 54 through 60 as well
as they are all just spam and off-topic (you can include mine as well).
I hope the guy stops spamming the bug tracker now seeing that these comments
don't really achieve anything.
Thanks for your help!
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2021-05-13 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 13:50 John Paul Adrian Glaubitz
2021-05-01 14:00 ` Frank Ch. Eigler
2021-05-13 21:33 ` John Paul Adrian Glaubitz
2021-05-13 22:54 ` Segher Boessenkool
2021-05-13 23:05 ` John Paul Adrian Glaubitz [this message]
2021-05-14 0:54 ` Frank Ch. Eigler
2021-05-14 6:45 ` John Paul Adrian Glaubitz
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=2c7a5314-d481-c61b-be8f-8b12aed42dfb@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=law@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=segher@kernel.crashing.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).