From: Joseph Myers <joseph@codesourcery.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: Re: Bugzilla admin permission to disable bugzilla accounts
Date: Thu, 11 Aug 2016 11:38:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1608111136030.31014@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CA+=Sn1kdGC6z=8jFsY-pVMdGVBmacVVm6uqqqu070S9xpBwprQ@mail.gmail.com>
On Thu, 11 Aug 2016, Andrew Pinski wrote:
> I am trying to help out with the bugzilla spam issue on gcc.gnu.org.
> Can someone give me (pinskia@gcc.gnu.org) bugzilla admin permissions
> to disable bugzilla accounts?
If you put a bug in the spam component and mark it RESOLVED/INVALID, that
should automatically disable the submitter's account. The most efficient
way of making all the changes to a bug is with the contrib/mark_spam.py
script (obviously, check carefully that all the bugs in a range really are
spam bugs before using it to mark a range of bugs as spam).
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2016-08-11 11:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 7:09 Andrew Pinski
2016-08-11 11:38 ` Joseph Myers [this message]
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=alpine.DEB.2.20.1608111136030.31014@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=overseers@gcc.gnu.org \
--cc=pinskia@gmail.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).