From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: "Frank Ch. Eigler" <fche@redhat.com>,
Overseers mailing list <overseers@sourceware.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
overseers@gcc.gnu.org, Richard Biener <rguenther@suse.de>
Subject: Re: Please lock bug report 92729 or ban abebeos@lazaridis.com from Bugzilla
Date: Fri, 14 May 2021 08:45:25 +0200 [thread overview]
Message-ID: <bb96afae-7dab-b379-6cc2-a38aa1b84ee9@physik.fu-berlin.de> (raw)
In-Reply-To: <20210514005411.GA13652@redhat.com>
Hello Frank!
On 5/14/21 2:54 AM, Frank Ch. Eigler wrote:
> Hi -
>
>> I hope the guy stops spamming the bug tracker now seeing that these comments
>> don't really achieve anything.
>
> Please take this dispute off the mailing lists and off
> bugzilla. No one comes off looking good here.
I have not been disputing anything. I have remained quiet after my last message
to the bug report on May, 1st when I also asked you to lock the bug report
and ban this user.
I don't know this guy and I'm not arguing with him, he is just spamming the mailing
lists and Bugzilla and I assume he will continue to do so unless his account gets
banned.
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
prev parent reply other threads:[~2021-05-14 6:45 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
2021-05-14 0:54 ` Frank Ch. Eigler
2021-05-14 6:45 ` John Paul Adrian Glaubitz [this message]
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=bb96afae-7dab-b379-6cc2-a38aa1b84ee9@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=fche@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=overseers@sourceware.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).