From: "Frank Ch. Eigler" <fche@redhat.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: overseers@gcc.gnu.org
Subject: Re: bugzilla spam
Date: Tue, 13 Mar 2012 10:44:00 -0000 [thread overview]
Message-ID: <20120313104346.GG17123@redhat.com> (raw)
In-Reply-To: <CAH6eHdRgR5PNXVhrrq4E6i48H2NH5x41eLvv2vhDsyJXxsV_AQ@mail.gmail.com>
Hi -
On Tue, Mar 13, 2012 at 09:47:51AM +0000, Jonathan Wakely wrote:
> [...]
> Is there a policy for removing spam comments such as this?
I think what's missing is mechanism, not policy. AFAIK,
bugzilla just doesn't have reasonable spam removal facilities.
- FChE
next prev parent reply other threads:[~2012-03-13 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 9:48 Jonathan Wakely
2012-03-13 10:44 ` Frank Ch. Eigler [this message]
2012-03-13 15:02 ` Paolo Carlini
2012-03-13 15:08 ` Frank Ch. Eigler
2012-03-14 10:38 ` Paolo Carlini
-- strict thread matches above, loose matches on Subject: below --
2007-04-17 4:17 Bugzilla spam Jeff Johnston
2007-04-17 4:26 ` Christopher Faylor
2007-04-17 6:09 ` Daniel Berlin
2007-04-17 10:59 ` Frank Ch. Eigler
2007-04-17 15:07 ` Daniel Berlin
2007-04-17 15:07 ` Daniel Berlin
2007-04-17 16:11 ` Jeff Johnston
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=20120313104346.GG17123@redhat.com \
--to=fche@redhat.com \
--cc=jwakely.gcc@gmail.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).