From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56707 invoked by alias); 11 Aug 2016 11:38:42 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 56690 invoked by uid 89); 11 Aug 2016 11:38:41 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:676, accounts X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 11 Aug 2016 11:38:31 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=SVR-IES-FEM-01.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1bXoJh-0007Ga-Ga from joseph_myers@mentor.com ; Thu, 11 Aug 2016 04:38:29 -0700 Received: from digraph.polyomino.org.uk (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.3.224.2; Thu, 11 Aug 2016 12:38:28 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.86_2) (envelope-from ) id 1bXoJe-0001TK-S3; Thu, 11 Aug 2016 11:38:26 +0000 Date: Thu, 11 Aug 2016 11:38:00 -0000 From: Joseph Myers To: Andrew Pinski CC: "overseers@gcc.gnu.org" Subject: Re: Bugzilla admin permission to disable bugzilla accounts In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2016-q3/txt/msg00049.txt.bz2 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