From: Paul Moore <pmoore@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LSM List <linux-security-module@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [GIT] Security subsystem upate for 3.18
Date: Mon, 13 Oct 2014 09:07:53 -0400 [thread overview]
Message-ID: <6097685.yy4GYjPioe@sifl> (raw)
In-Reply-To: <alpine.LRH.2.11.1410131502510.6957@namei.org>
On Monday, October 13, 2014 03:06:34 PM James Morris wrote:
> On Sun, 12 Oct 2014, Linus Torvalds wrote:
> > on some previous development, so it's often a good time to simply
> > create a new feature branch. I don't know how James feels about
> > merging multiple separate feature branches, but I know that *I* tend
> > to appreciate it when I get multiple well-defined pull requests rather
> > than one big one that does many different things.
>
> It's fine with me.
>
> This is the first time I saw (or noticed) that Paul had back merged ahead
> of me, but it seemed to merge into my tree ok so I didn't query it at the
> time.
The management of the linux-security tree, the approach I was taking with the
SELinux tree, and the approach that the other LSM maintainers use has been
discussed many times on the LSM list. I'm also fairly certain that you were
on the To/CC line for many, if not all, of those threads.
--
paul moore
security and virtualization @ redhat
next prev parent reply other threads:[~2014-10-13 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 8:23 [GIT] Security subsystem upate for 3.18 James Morris
2014-10-12 14:12 ` Linus Torvalds
2014-10-12 14:32 ` Linus Torvalds
2014-10-12 15:04 ` Paul Moore
2014-10-12 15:50 ` Linus Torvalds
2014-10-12 16:01 ` Linus Torvalds
2014-10-13 4:06 ` James Morris
2014-10-13 13:07 ` Paul Moore [this message]
2014-10-14 11:01 ` James Morris
2014-10-12 21:19 ` Paul Moore
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=6097685.yy4GYjPioe@sifl \
--to=pmoore@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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