| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAOesGMjotnx_6HiwngRO9OaZYGGAexiwZ_shkOK7qROZcjDmqA@mail.gmail.com> Date: Thu, 4 Oct 2012 09:55:27 -0700 From: Olof Johansson <olof@...om.net> To: Stephen Boyd <sboyd@...eaurora.org> Cc: arm@...nel.org, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Linux Kernel <linux-kernel@...r.kernel.org> Subject: Re: arm-soc maintainer entry Hi, On Thu, Oct 4, 2012 at 1:41 AM, Stephen Boyd <sboyd@...eaurora.org> wrote: > Is the arm@...nel.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@...nel.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. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists