From: James Morris <james.l.morris@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paul Moore <paul@paul-moore.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: linux-next: the selinux tree needs cleaning up
Date: Fri, 27 Jun 2014 12:41:21 +1000 [thread overview]
Message-ID: <53ACD9D1.2010803@oracle.com> (raw)
In-Reply-To: <20140626081232.52cb51da@canb.auug.org.au>
On 06/26/2014 08:12 AM, Stephen Rothwell wrote:
> Hi James,
>
> On Wed, 25 Jun 2014 20:51:43 +1000 James Morris <james.l.morris@oracle.com> wrote:
>>
>> I haven't pulled in Paul's tree, I merged with the latest Linus release.
>
> Ummm, yesterday your security tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git#next)
> moved from commit 2fd4e6698f08 ("Merge branch 'smack-for-3.16' of
> git://git.gitorious.org/smack-next/kernel into next") (which is
> included in v3.16-rc1) to commit f01387d26938 ("Merge commit 'v3.15'
> into next"). The commit between those 2 commits is 92953ff38ba5
> ("Merge branch 'next' of git://git.infradead.org/users/pcmoore/selinux
> into next").
>
Ok, I thought you meant pulled in more recently.
next prev parent reply other threads:[~2014-06-27 2:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 22:40 linux-next: the selinux tree needs cleaning up Stephen Rothwell
2014-06-18 18:26 ` Paul Moore
2014-06-19 15:08 ` Stephen Rothwell
2014-06-19 19:47 ` Paul Moore
2014-06-19 22:59 ` Stephen Rothwell
2014-06-20 3:43 ` Serge E. Hallyn
2014-06-20 3:59 ` Stephen Rothwell
2014-06-20 14:57 ` Serge E. Hallyn
2014-06-20 16:06 ` Paul Moore
2014-06-24 18:03 ` Paul Moore
2014-06-24 23:59 ` Stephen Rothwell
2014-06-25 10:51 ` James Morris
2014-06-25 22:12 ` Stephen Rothwell
2014-06-27 2:41 ` James Morris [this message]
2014-06-25 14:14 ` 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=53ACD9D1.2010803@oracle.com \
--to=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.com \
--cc=sfr@canb.auug.org.au \
/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.