mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Moving unseen/inactive MAINTAINER M: names and email addresses to CREDITS
Date: Fri, 29 May 2015 04:20:48 +0100	[thread overview]
Message-ID: <1432869648.6319.48.camel@decadent.org.uk> (raw)
In-Reply-To: <1432843185.1556.19.camel@perches.com>

[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]

On Thu, 2015-05-28 at 12:59 -0700, Joe Perches wrote:
> On Wed, 2015-05-27 at 14:06 -0700, Andrew Morton wrote:
> > On Wed, 27 May 2015 14:01:44 -0700 Joe Perches <joe@perches.com> wrote:
> > > There are about 950 unique M: names in MAINTAINERS.
> > > 
> > > About 200 of those names haven't signed or authored a
> > > single commit in 3+ years.
> > > 
> > > Any desire to shorten the MAINTAINERS entries and orphan
> > > or delete those sections that that seem to have a single
> > > apparently inactive maintainer?
> > > 
> > > Maybe 25 of those M: entries are actually email exploder
> > > type uses that should likely stay listed.
> > 
> > Yes, I suppose we should clean this up.  At present we're misleading
> > people about the likely outcome of their emails.  And we're misleading
> > people (like me) who see the email and think "ok, someone's taking care
> > of that".
> 
> This is the list of maintainer names/sections that seem
> not to have signed, authored or acked a commit in 3 years.
> 
> After some editing and additional grepping, I got 133 entries.
> 
> The grep patterns I used are imperfect.
> 
> For instance, the MAINTAINERS file has "Hideaki Yoshifuji" but
> he doesn't ever sign anything that way.  His signature is
> "Yoshifuji Hideaki".
> 
> If anyone sees any obvious false-positives, please let me know.
> 
> I'll send a private email to all these people and see if they
> want to be listed in the MAINTAINERS file and see what happens.
> 
> Here is the list two ways, alphabetic by name and by section
[...]
> Eric Piel <eric.piel@tremplin-utc.net>            	LIS3LV02D ACCELEROMETER DRIVER

I see a few Reviewed-by: Éric Piel <eric.piel@tremplin-utc.net> (note
the added accent).

[...]
> Tony Finch <dot@dotat.at>                         	UNIFDEF
[...]

He's still upstream maintainer for unifdef, even if we haven't updated
our embedded copy.

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an expert.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

  reply	other threads:[~2015-05-29  3:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 21:01 Joe Perches
2015-05-27 21:06 ` Andrew Morton
2015-05-28 19:59   ` Joe Perches
2015-05-29  3:20     ` Ben Hutchings [this message]
2015-05-29  3:25       ` Joe Perches
2015-05-29  6:58     ` Sudip Mukherjee
2015-05-29 15:38     ` Laura Abbott
2015-05-29 16:35       ` Joe Perches
2015-06-23 18:49         ` Pavel Machek
2015-06-23 20:02           ` Joe Perches

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=1432869648.6319.48.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome