From: Ian Lance Taylor <iant@google.com>
To: Torbjorn Granlund <tg@gmplib.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Reporting GCC bugs
Date: Tue, 09 Oct 2012 16:08:00 -0000 [thread overview]
Message-ID: <CAKOQZ8xg=MZAEa7X4LzkvgwRnXqFcFHUdBRdPEMV9JfsmWDz-g@mail.gmail.com> (raw)
In-Reply-To: <86r4p766jh.fsf@shell.gmplib.org>
On Tue, Oct 9, 2012 at 7:53 AM, Torbjorn Granlund <tg@gmplib.org> wrote:
> I tried to report two gcc bugs today. I read the
> http://gcc.gnu.org/bugs/ page, and then clicked on the link for making
> the actual report. I was then--without motivation--requested to create
> an "account".
>
> I am not happy maintaining lots of "accounts" for this and that. Since
> there is no motivation whatsoever why an account would be needed, I will
> not create one, and will not send in any gcc bug reports for the time
> being.
I'm certainly sorry to hear that you will not be reporting bugs for
GCC. However, we have had spam in bugzilla in the past, and it's a
real pain to deal with. It's even led us to being added to e-mail
blacklists, and cleaning that up was hours of my life that I will
never get back. Requiring an account with a valid e-mail address is
an unfortunate necessity on the current Internet, at least for a
popular and well-known site like gcc.gnu.org. I wish it were not so,
but the fault is not with the GCC project; it is with the spammers.
Ian
next prev parent reply other threads:[~2012-10-09 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 14:53 Torbjorn Granlund
2012-10-09 16:08 ` Ian Lance Taylor [this message]
2012-10-09 16:40 ` Torbjorn Granlund
2012-10-09 18:23 ` Paul Smith
2012-10-10 15:54 ` Ian Lance Taylor
2012-10-11 14:59 ` Ludovic Courtès
2012-10-11 16:28 ` Ian Lance Taylor
[not found] ` <CAF1jjLsRRWLQm_vfdzSDBVVFc_-UG0=v17PTFbZcnjcBD-x4wQ@mail.gmail.com>
[not found] ` <CAKOQZ8zOxNiPSpsPh0DUAw_JuLehkoeAza968bzD1qPuoMJ7bg@mail.gmail.com>
[not found] ` <CAH6eHdTN=KxUB8VQUg9S1myzJU4CthoLSSgTXMr-Cz6R+aj0sg@mail.gmail.com>
2012-11-02 14:32 ` Ángel González
2012-11-30 5:33 ` NightStrike
2012-11-30 5:37 ` Ian Lance Taylor
2012-11-30 12:23 ` Frédéric Buclin
2012-11-30 12:35 ` NightStrike
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='CAKOQZ8xg=MZAEa7X4LzkvgwRnXqFcFHUdBRdPEMV9JfsmWDz-g@mail.gmail.com' \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=tg@gmplib.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).