From: Paul Moore <paul@paul-moore.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
"Serge E. Hallyn" <serge@canonical.com>
Subject: Re: Change in security maintainer for a few weeks
Date: Thu, 05 Jun 2014 18:39:09 -0400 [thread overview]
Message-ID: <4426926.gIRHbeKnmD@sifl> (raw)
In-Reply-To: <alpine.LRH.2.00.1406052355500.2434@twin.jikos.cz>
On Thursday, June 05, 2014 11:59:11 PM Jiri Kosina wrote:
> 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@oracle.com> (supporter:SECURITY SUBSYSTEM)
> ...
>
> 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.
Once several of us became aware that James was stepping away for a few weeks
(I should mention this was not a planned absence and took most of us by
surprise) we had a brief discussion off-list and several of us did offer to
"step-up"; Serge had already created a repo and since he had pushed patches
while James was away in the past it seemed a reasonable approach this time
around.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2014-06-05 22:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 18:30 Change in security maintainer for a few weeks Greg KH
2014-06-05 18:38 ` Josh Boyer
2014-06-05 18:47 ` Serge E. Hallyn
2014-06-05 18:52 ` Greg KH
2014-06-05 18:55 ` Serge E. Hallyn
2014-06-05 22:54 ` Greg KH
2014-06-05 19:52 ` Dmitry Kasatkin
2014-06-06 3:26 ` Mimi Zohar
2014-06-05 21:51 ` Tetsuo Handa
2014-06-05 21:59 ` Jiri Kosina
2014-06-05 22:39 ` Paul Moore [this message]
2014-06-05 22:53 ` Greg KH
2014-06-06 4:42 ` Serge Hallyn
2014-06-06 15:08 ` Casey Schaufler
2014-06-06 15:23 ` Serge E. Hallyn
2014-06-06 15:41 ` Casey Schaufler
2014-06-10 5:20 ` James Morris
2014-06-10 20:23 ` Greg KH
2014-06-11 1:34 ` Mimi Zohar
2014-06-11 2:49 ` Serge E. Hallyn
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=4426926.gIRHbeKnmD@sifl \
--to=paul@paul-moore.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@canonical.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.