From: Serge Hallyn <serge.hallyn@ubuntu.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Paul Moore <paul@paul-moore.com>, Jiri Kosina <jkosina@suse.cz>,
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: Fri, 6 Jun 2014 04:42:01 +0000 [thread overview]
Message-ID: <20140606044201.GG22106@ubuntumail> (raw)
In-Reply-To: <20140605225311.GB32470@kroah.com>
Quoting Greg KH (gregkh@linuxfoundation.org):
> On Thu, Jun 05, 2014 at 06:39:09PM -0400, Paul Moore wrote:
> > 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.
>
> That's great, as the communication around this has not been very much
> (an non-existant on the subsystem mailing list) I was not aware of it.
>
> If Serge wants to do this, and as he has been the stand-in for James in
> the past, I have _no_ objection to this at all.
>
> Serge, feel free to resend your patches to Linus if he doesn't pick them
> up in a few days, with the information that you are doing this in
> James's absence for a while.
Will do (and wil cc: lsm).
> So, that was easy, I don't have to do this at all, great.
>
> greg k-h
next prev parent reply other threads:[~2014-06-06 4:42 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
2014-06-05 22:53 ` Greg KH
2014-06-06 4:42 ` Serge Hallyn [this message]
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=20140606044201.GG22106@ubuntumail \
--to=serge.hallyn@ubuntu.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox