From: james.l.morris@oracle.com (James Morris)
To: linux-security-module@vger.kernel.org
Subject: Security subsystem tree merge to v4.15-rc3
Date: Wed, 20 Dec 2017 07:34:17 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1712200733540.15646@localhost> (raw)
In-Reply-To: <fd51caa9-4281-daa1-3cef-98f791cddff4@schaufler-ca.com>
On Mon, 18 Dec 2017, Casey Schaufler wrote:
> On 12/10/2017 10:05 PM, James Morris wrote:
> > For developers working against the security subsystem tree,
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
> >
> > this is now merged to Linus' v4.15-rc3.
>
> I'm not clear on how you want the next-smack branch managed. Do you
> want me to merge in next-general, or keep it relative to 4.13?
Merge to next-general.
--
James Morris
<james.l.morris@oracle.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-12-19 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 6:05 Security subsystem tree merge to v4.15-rc3 James Morris
2017-12-11 21:55 ` Mimi Zohar
2017-12-18 19:28 ` Casey Schaufler
2017-12-19 20:34 ` James Morris [this message]
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=alpine.LFD.2.20.1712200733540.15646@localhost \
--to=james.l.morris@oracle.com \
--cc=linux-security-module@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).