public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@elastic.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: overseers@gcc.gnu.org,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Richard Biener <rguenther@suse.de>,
	Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: Please lock bug report 92729 or ban abebeos@lazaridis.com from Bugzilla
Date: Sat, 1 May 2021 10:00:55 -0400	[thread overview]
Message-ID: <YI1fF65qE2Zj8urw@elastic.org> (raw)
In-Reply-To: <835e0073-07e6-9895-fc72-3113cba43f26@physik.fu-berlin.de>

Hi -

> The user abebeos@lazaridis.com repeatedly tries to make claims to
> the Bountysource campaign for converting the AVR backend to MODE_CC
> [1]. [...]

(this is not an overseer relevant issue)


> Could you either lock the bug report 92729 [1] or ban the user
> abebeos@lazaridis.com altogether? I usually do not endorse such
> bans, but this guy is starting to become really annoying by spamming
> the mailing list and/or bugzilla.

I see a handful of messages over the last few days, and you are a
party to the conversation.  Sorry, this does not seem to constitute
evidence that there is a consensus of a serious enough problem.

Please try to resolve the issue outside bugzilla.

- FChE

  reply	other threads:[~2021-05-01 14:01 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 [this message]
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

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=YI1fF65qE2Zj8urw@elastic.org \
    --to=fche@elastic.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --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).