public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Torbjorn Granlund <tg@gmplib.org>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Reporting GCC bugs
Date: Tue, 09 Oct 2012 16:40:00 -0000	[thread overview]
Message-ID: <86626j38ft.fsf@shell.gmplib.org> (raw)
In-Reply-To: <CAKOQZ8xg=MZAEa7X4LzkvgwRnXqFcFHUdBRdPEMV9JfsmWDz-g@mail.gmail.com> (Ian Lance Taylor's message of "Tue\, 9 Oct 2012 09\:08\:14 -0700")

Ian Lance Taylor <iant@google.com> writes:

  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.

Thanks for the reply!

I had no idea this was due to spamming problems.

I think the explanation you provide really should be on the page I
indicated.

The GMP lists also receive spam attempts, a handful per day.  I deal
with it manually, and with whitelists for known non-spammers.  The
disadvantage is that it takes perhaps a minute of the moderators' time
each day, and that people see delays in reaching the lists.

The GCC way surely deflects spam, but also surely deflects lots of bug
reports, in particular when no valid explanation for the need of
registration is given.

-- 
Torbjörn

  reply	other threads:[~2012-10-09 16:40 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
2012-10-09 16:40   ` Torbjorn Granlund [this message]
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=86626j38ft.fsf@shell.gmplib.org \
    --to=tg@gmplib.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.com \
    /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).