From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932260AbcHZSB3 (ORCPT ); Fri, 26 Aug 2016 14:01:29 -0400 Received: from mail-pf0-f172.google.com ([209.85.192.172]:33387 "EHLO mail-pf0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932212AbcHZSB2 (ORCPT ); Fri, 26 Aug 2016 14:01:28 -0400 Subject: Re: MAINTAINERS without commits in the last 3 years To: Joe Perches , LKML References: <1472081625.3746.217.camel@perches.com> From: Florian Fainelli Message-ID: <0c04b145-4322-c1e7-2a77-b0d6eaee2dee@gmail.com> Date: Fri, 26 Aug 2016 09:56:48 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <1472081625.3746.217.camel@perches.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/24/2016 04:33 PM, Joe Perches wrote: > Many email addresses in MAINTAINERS no longer work so many > sections in > MAINTAINERS could likely be considered either > obsolete or unmaintained. > > Marking these sections appropriately or simply removing the > sections would make MAINTAINERS and get_maintainer.pl more > useful. > > These M: entries in MAINTAINERS haven't authored or had any > -by: signature entries in git log for the last 3 years. > > Some of these, like stable@kernel.org and trivial@kernel.org, are > obviously addresses that should not be deleted from MAINTAINERS, > but most of them are candidates for removal or update. > > The email addresses below are also bcc'd here to see what bounces. > The list of the bounces will be collected. > > Thoughts? > For: > bcm-kernel-feedback-list@broadcom.com This mailing-list was recently added under the M: entry with commit 086f470481f5305ac52ce960e31a7d4441886e59 ("MAINTAINERS: Change L to M for Broadcom ARM/ARM64 SoC entries") (was L: before) since no external (to Broadcom) subscribers are allowed. Should we add a new tag for that kind of entry? -- Florian