From: Olof Johansson <olof@lixom.net>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: arm@kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: arm-soc maintainer entry
Date: Thu, 4 Oct 2012 12:28:08 -0700 [thread overview]
Message-ID: <CAOesGMgng=OLWT3AwWcvkDQwVAoQknJ5bdZVF__fwSD6WfbkQQ@mail.gmail.com> (raw)
In-Reply-To: <506DDA31.9010503@codeaurora.org>
On Thu, Oct 4, 2012 at 11:49 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
> On 10/04/12 09:55, Olof Johansson wrote:
>> Hi,
>>
>> On Thu, Oct 4, 2012 at 1:41 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>>> Is the arm@kernel.org alias going to be added into the MAINTAINERS file?
>>> Should anybody be sending mails to this address?
>>>
>>> It seems I asked this over a year ago and the response was positive but
>>> nothing ever happened[1]. Maybe something like below? I only ask because
>>> get_maintainer.pl isn't picking up this email.
>> I've been holding off re-proposing this, mostly because life is easier
>> for us if we don't get arm@kernel.org cc:d on every single patch by
>> people who run get_maintainers.pl -- it's the equivalent of getting
>> linux-arm-kernel cc:d to your inbox. It's better signal-to-noise ratio
>> if it's mostly platform maintainers that email us on that address with
>> pull requests or patches they want applied.
>>
>> But yeah, it also means that the maintainer structure is undocumented.
>> I'm open for suggestions.
>>
>
> Thanks for clarifying. Maybe we can put in the git tree and no email
> address? That at least documents some structure.
Ah, yes, that makes a lot of sense.
-Olof
prev parent reply other threads:[~2012-10-04 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 8:41 arm-soc maintainer entry Stephen Boyd
2012-10-04 16:55 ` Olof Johansson
2012-10-04 18:49 ` Stephen Boyd
2012-10-04 19:28 ` Olof Johansson [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='CAOesGMgng=OLWT3AwWcvkDQwVAoQknJ5bdZVF__fwSD6WfbkQQ@mail.gmail.com' \
--to=olof@lixom.net \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@codeaurora.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).