From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751349AbcGMVxg (ORCPT ); Wed, 13 Jul 2016 17:53:36 -0400 Received: from yosemitenews.info ([162.210.197.196]:34716 "EHLO lw1.spinics.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751082AbcGMVx1 (ORCPT ); Wed, 13 Jul 2016 17:53:27 -0400 X-Greylist: delayed 1025 seconds by postgrey-1.27 at vger.kernel.org; Wed, 13 Jul 2016 17:53:27 EDT From: ellis@spinics.net Message-Id: <201607132135.u6DLZEvS030590@spinics.net> Subject: Re: Bugzilla spam To: mtk.manpages@gmail.com Date: Wed, 13 Jul 2016 14:35:14 -0700 (PDT) Cc: mricon@kernel.org (Konstantin Ryabitsev), linux-man@vger.kernel.org (linux-man), linux-kernel@vger.kernel.org (lkml) In-Reply-To: X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Okay, thanks. In the meantime, is it possible for you to lock the > man-pages component so that no further bug reports can be made via > that component? It's not just the man-pages component. I'm seeing the same spam starting up on backports.