[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.00.1406052355500.2434@twin.jikos.cz>
Date: Thu, 5 Jun 2014 23:59:11 +0200 (CEST)
From: Jiri Kosina <jkosina@...e.cz>
To: Greg KH <gregkh@...uxfoundation.org>
cc: linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: Re: Change in security maintainer for a few weeks
On Thu, 5 Jun 2014, Greg KH wrote:
> James has had to step back from doing kernel work for a few weeks, so
> I've offered to step up and handle the security patches to get shuttled
> to Linus for merging for a while.
As exactly this (working with active contributors to help co-maintain the
subsystem) has been brought at the ksummit maling list, I am just curious
whether noone else actively working in that area was willing to step up?
$ ./scripts/get_maintainer.pl --git -f security/
James Morris <james.l.morris@...cle.com> (supporter:SECURITY SUBSYSTEM)
Mimi Zohar <zohar@...ux.vnet.ibm.com> (commit_signer:51/220=23%)
Paul Moore <pmoore@...hat.com> (commit_signer:43/220=20%,authored:24/220=11%)
Eric Paris <eparis@...hat.com> (commit_signer:43/220=20%,authored:16/220=7%)
David Howells <dhowells@...hat.com> (commit_signer:29/220=13%,authored:24/220=11%)
Roberto Sassu <roberto.sassu@...ito.it> (commit_signer:24/220=11%,authored:19/220=9%)
John Johansen <john.johansen@...onical.com> (authored:20/220=9%)
If not, then I think this can be shown as a prime example why the problem
of "non-substituability" of many maintainers is actually real.
Thanks,
--
Jiri Kosina
SUSE Labs
--
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