public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Paolo Carlini <paolo.carlini@oracle.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, overseers@gcc.gnu.org
Subject: Re: bugzilla spam
Date: Tue, 13 Mar 2012 15:02:00 -0000	[thread overview]
Message-ID: <4F5F60CD.50505@oracle.com> (raw)
In-Reply-To: <20120313104346.GG17123@redhat.com>

On 03/13/2012 11:43 AM, Frank Ch. Eigler wrote:
> 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.
I see. Still, in the past I thought to myself multiple times that it 
seems strange that in general we can only *add* to the audit trail, 
nothing can be removed. I understand that can be also a freedom of 
expression issue, if you see what I mean, but in some extreme cases, 
like pure and obvious spam, shouldn't we have a way to remove things?!? 
Maybe somebody, endowed with appropriate privileges, should simply do 
that by hand, on a case by case basis?

Thanks,
Paolo.

  reply	other threads:[~2012-03-13 15:02 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
2012-03-13 15:02   ` Paolo Carlini [this message]
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=4F5F60CD.50505@oracle.com \
    --to=paolo.carlini@oracle.com \
    --cc=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).