From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org
Subject: GCC/classpath bugzilla spam
Date: Tue, 26 Jul 2016 18:07:00 -0000 [thread overview]
Message-ID: <20160726180721.GA3644@blokker> (raw)
Hi,
GNU Classpath uses the GCC bugzilla for issue tracking.
It seems there is a large flood of spam the last two days.
I see around 50 new spam bugs being opened just the last 6 hours.
See https://lists.gnu.org/archive/html/bug-classpath/2016-07/index.html
Unfortunately I am travelling and don't have easy internet access.
Could someone take a look to see if there can be anything done
to stop people creating new "spam" bugs?
Thanks,
Mark
next reply other threads:[~2016-07-26 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 18:07 Mark Wielaard [this message]
2016-07-26 18:33 ` Frank Ch. Eigler
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=20160726180721.GA3644@blokker \
--to=mark@klomp.org \
--cc=overseers@sourceware.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).