From: "Daniel Berlin" <dberlin@dberlin.org>
To: overseers@gcc.gnu.org, "Mark Mitchell" <mark@codesourcery.com>
Subject: FYI: michelin60@gmail.com banned from gcc bugzilla
Date: Tue, 04 Sep 2007 02:11:00 -0000 [thread overview]
Message-ID: <4aca3dc20709031911w168a296csbfd77a6f86d4d8cd@mail.gmail.com> (raw)
This was done at the request of two gcc developers (I try to be
neutral in these things, and rely on what others think should be
done).
He seems to alternate between being sane and polite, and spouting vast
conspiracy theories (which sadly is not helped by Andrew responding to
him continually), with no middle ground.
See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33277#c5
and http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33277#c1
and http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33252#c10
and ....
He has repeatedly reopened bugs that have been closed by gcc
developers, even after being told no to.
I only mention it here as he might protest to his banning, feel free
to send him my way.
reply other threads:[~2007-09-04 2:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4aca3dc20709031911w168a296csbfd77a6f86d4d8cd@mail.gmail.com \
--to=dberlin@dberlin.org \
--cc=mark@codesourcery.com \
--cc=overseers@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).