From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org>
To: overseers@gcc.gnu.org
Subject: [Bug web/72856] Trottle bug creation for newly created accounts (to limit spam)
Date: Wed, 10 Aug 2016 08:33:00 -0000 [thread overview]
Message-ID: <bug-72856-5127-0NLRFybGWw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-72856-5127@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72856
Gerald Pfeifer <gerald at pfeifer dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gerald at pfeifer dot com
--- Comment #2 from Gerald Pfeifer <gerald at pfeifer dot com> ---
Thanks for looking into this, Frédéric!
As for rate throttling, how about only allowing for a single bug
report per day until a bug report has been "processed" (for some
suitable definition of "processed" - perhaps even any action that
is different from simply marking it as spam)?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-08-10 8:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 2:43 [Bug web/72856] New: " LpSolit at netscape dot net
2016-08-10 2:44 ` [Bug web/72856] " LpSolit at netscape dot net
2016-08-10 5:50 ` trippels at gcc dot gnu.org
2016-08-10 8:33 ` gerald at pfeifer dot com [this message]
2016-08-10 11:46 ` manu at gcc dot gnu.org
2016-08-10 12:04 ` LpSolit at netscape dot net
2016-08-10 12:33 ` LpSolit at netscape dot net
2016-08-10 12:41 ` fche at redhat dot com
2016-08-11 11:58 ` joseph at codesourcery dot com
2016-08-15 19:57 ` redi at gcc dot gnu.org
2016-08-16 14:41 ` LpSolit at netscape dot net
2016-08-22 20:10 ` bernd.edlinger at hotmail dot de
2016-08-23 6:07 ` [Bug web/72856] Throttle " gerald at pfeifer dot com
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=bug-72856-5127-0NLRFybGWw@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--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).