From: David Dillow <dave@thedillows.org>
To: Joe Perches <joe@perches.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: MAINTAINERS drivers/net cleanups?
Date: Mon, 19 Oct 2009 11:24:44 -0400 [thread overview]
Message-ID: <1255965884.32011.13.camel@lap75545.ornl.gov> (raw)
In-Reply-To: <1255729936.2267.179.camel@Joe-Laptop.home>
On Fri, 2009-10-16 at 14:52 -0700, Joe Perches wrote:
> Ben Hutchings suggested adding a facility to
> scripts/get_maintainer.pl to print the role of
> each maintainer. I added a bit more to print
> statistics about the maintainers and "-by:" lines
> from each git commit as well.
[snip script]
> There are many people described as MAINTAINERS for
> these files that have not had a single sign-off or
> commit in git history.
Uhm, I think your script is broken, as I've patched typhoon this year.
I've also ACKed a few patches that have been sent to me, and tried to
watch the list for patches that weren't.
> Should these individuals be removed from MAINTAINERS
> and added to CREDITS if not already there?
I think you should try to contact the ones listed and see if they are
still actively watching for their drivers. I've not had to do a lot to
typhoon, as there is no new hardware coming out, and while I've sent in
several Acked-by's, not all of them have made it to the final commit.
Just because there are few patches from the person listed as maintainer
does not mean they are not keeping an eye on things.
> ------> drivers/net/typhoon.c
> David Dillow <dave@thedillows.org> (maintainer)
>
> 3CR990 NETWORK DRIVER
> M: David Dillow <dave@thedillows.org>
> L: netdev@vger.kernel.org
> S: Maintained
> F: drivers/net/typhoon*
prev parent reply other threads:[~2009-10-19 16:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 21:52 MAINTAINERS drivers/net cleanups? Joe Perches
2009-10-17 10:55 ` Krzysztof Halasa
2009-10-17 11:52 ` Denys Fedoryschenko
2009-10-19 15:24 ` David Dillow [this message]
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=1255965884.32011.13.camel@lap75545.ornl.gov \
--to=dave@thedillows.org \
--cc=joe@perches.com \
--cc=netdev@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).