From: Segher Boessenkool <segher@kernel.crashing.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
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: Thu, 13 May 2021 17:54:47 -0500 [thread overview]
Message-ID: <20210513225447.GH10366@gate.crashing.org> (raw)
In-Reply-To: <13ce1b17-91f1-2773-d2eb-978977e71564@physik.fu-berlin.de>
Hi Adrian,
On Thu, May 13, 2021 at 11:33:44PM +0200, John Paul Adrian Glaubitz wrote:
> On 5/1/21 3:50 PM, John Paul Adrian Glaubitz wrote:
> > The user abebeos@lazaridis.com repeatedly tries to make claims to the Bountysource
> > campaign for converting the AVR backend to MODE_CC [1]. Since he did not contribute
> > any of the code that got eventually committed - the work was done by Senthil Kumar -
> > he has no right to claim any of the money of the bounty for the Bountysource campaign.
>
> 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.
Segher
next prev parent reply other threads:[~2021-05-13 22:55 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 [this message]
2021-05-13 23:05 ` John Paul Adrian Glaubitz
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=20210513225447.GH10366@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=law@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).