From: Joe Perches <joe@perches.com>
To: Anders Larsen <al@alarsen.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: MAINTAINERS without commits in the last 3 years
Date: Tue, 30 Aug 2016 08:35:50 -0700 [thread overview]
Message-ID: <1472571350.5512.78.camel@perches.com> (raw)
In-Reply-To: <11802301.9dQfm9VpCT@oscar>
On Tue, 2016-08-30 at 17:19 +0200, Anders Larsen wrote:
> On Wednesday, 2016-08-24 16:33 Joe Perches wrote:
> > Many email addresses in MAINTAINERS no longer work so many
> > sections in MAINTAINERS could likely be considered either
> > obsolete or unmaintained.
> Whereas I agree it's helpful to purge dysfunctional adresses...
> > These M: entries in MAINTAINERS haven't authored or had any
> > -by: signature entries in git log for the last 3 years.
> ...IMHO just because there hasn't been any activity for
> amount of time> does not automatically mean the subsystem in question
> has been abandoned.
Nor does it mean that address/person would be purged unless
specifically requested or the email bounces.
Even if an email bounces, there are sometimes simple updates
for dead addresses like rml's tech9.
But unless you try/ask, you can't know if someone doesn't want
to be/isn't a maintainer anymore. I've had a few "I'm not
doing this anymore, remove me" type replies.
> I'm using "my" subsystem (QNX4 FS) almost daily, so I don't believe
> anything would be gained if get_maintainers.pl would stop keeping me
> in the loop.
Good on you.
next prev parent reply other threads:[~2016-08-30 15:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 23:33 MAINTAINERS without commits in the last 3 years Joe Perches
[not found] ` <CA+i2_Ddvg9a0S23ywJtXQbLuq3JLJF9poH=n_G1+9uWWVPZwOg@mail.gmail.com>
2016-08-25 0:24 ` Joe Perches
[not found] ` <CAHrUA37xh-6GLkTAM75w8v550rR8n2Ayycjy9FNofv3K+=QoVQ@mail.gmail.com>
2016-08-25 2:09 ` Joe Perches
2016-08-25 3:26 ` Alexander Graf
2016-08-25 7:01 ` Ali Akcaagac
2016-08-25 7:29 ` Steve Twiss
2016-08-25 10:12 ` Mauro Carvalho Chehab
2016-08-25 16:12 ` David Carroll
2016-08-25 20:46 ` Steven French
2016-08-25 20:58 ` Greg KH
2016-08-26 0:33 ` Joe Perches
2016-08-26 12:59 ` Shuah Khan
2016-08-26 16:56 ` Florian Fainelli
2016-08-26 17:09 ` Joe Perches
2016-08-26 19:34 ` Jason Baron
2016-08-26 19:50 ` Joe Perches
2016-08-26 20:05 ` Borislav Petkov
2016-08-26 20:17 ` Luck, Tony
2016-09-01 12:58 ` Borislav Petkov
2016-09-01 16:02 ` Joe Perches
2016-09-02 5:26 ` Borislav Petkov
[not found] ` <CACwGpODqLAjQxgw=EdtWCKhFywy9btv9Ka6XG8YXbzKEBFPzEg@mail.gmail.com>
2016-08-28 2:40 ` Joe Perches
2016-08-30 15:19 ` Anders Larsen
2016-08-30 15:35 ` Joe Perches [this message]
2016-08-25 10:00 Tigran Aivazian
2016-08-25 10:09 ` 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=1472571350.5512.78.camel@perches.com \
--to=joe@perches.com \
--cc=al@alarsen.net \
--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;
as well as URLs for NNTP newsgroup(s).