From: David Rientjes <rientjes@google.com>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Mike Waychison <mikew@google.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] firmware/google: drop 'select EFI' to avoid recursive dependency
Date: Fri, 24 Jan 2014 02:27:32 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1401240221370.9846@chino.kir.corp.google.com> (raw)
In-Reply-To: <1390521727.32356.16.camel@joe-AO722>
On Thu, 23 Jan 2014, Joe Perches wrote:
> > > get_maintainer's default output should answer the question "who do I
> > > email about this file", and that ain't working :(
>
> Complaints cheerfully ignored.
> Suggestions gratefully accepted.
>
> Files that haven't had changes in a long time
> generally aren't maintained.
>
> Old addresses frequently become stale and bounce.
>
> It'd be better if there was a MAINTAINERS entry
> for drivers/firmware/google.
>
I think scripts/get_maintainer.pl is only really useful for emailing
patches so I think outputting at least somebody to cc on patches would be
a good idea. It doesn't necessarily need to be someone who maintains the
code and pushes it to Linus.
I'm not sure how much runtime is a factor for people of the script, but
falling back to git-blame behavior to at least get one or two cc's sounds
appropriate. If the email address is outdated, owell, we live and learn.
Otherwise it just seems like people would throw patches at a wall and see
which ones stick.
Now, if Andrew wants an all-encompasing MAINTAINERS entry that really
lists all the directories he maintains, that would be fine as well just as
long as we're ok with the size of MAINTAINERS doubling :)
next prev parent reply other threads:[~2014-01-24 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 10:39 Ard Biesheuvel
2014-01-23 21:36 ` David Rientjes
2014-01-23 21:40 ` Mike Waychison
2014-01-23 21:48 ` Ard Biesheuvel
2014-01-23 21:49 ` Andrew Morton
2014-01-23 22:45 ` David Rientjes
2014-01-24 0:02 ` Joe Perches
2014-01-24 10:27 ` David Rientjes [this message]
2014-01-24 22:56 ` Joe Perches
2014-01-24 23:17 ` David Rientjes
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=alpine.DEB.2.02.1401240221370.9846@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
/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
all inboxes | Powered by JetHome®