Paul Moore
2017-09-20 16:01:03 UTC
If you've been following the SELinux and LSM mailing lists over the
past couple of weeks you know that there has been a shift in how the
SELinux kernel tree feeds into Linus' tree: we are now sending pull
request directly to Linus. As part of this change I'm now going to be
basing the selinux/next branch on Linus' tree instead of the
linux-security/next; other than this change the process should be
pretty much the same.
The only immediate effect you may notice is that selinux/next is now
currently based on v4.14-rc1. This is a side-effect of the
changeover, future rebases will aim to be based on major releases when
possible.
I've updated my blog post from earlier in the year for those who may
not be familiar on the process:
* http://www.paul-moore.com/blog/d/2017/07/kernel-repo-process.html
past couple of weeks you know that there has been a shift in how the
SELinux kernel tree feeds into Linus' tree: we are now sending pull
request directly to Linus. As part of this change I'm now going to be
basing the selinux/next branch on Linus' tree instead of the
linux-security/next; other than this change the process should be
pretty much the same.
The only immediate effect you may notice is that selinux/next is now
currently based on v4.14-rc1. This is a side-effect of the
changeover, future rebases will aim to be based on major releases when
possible.
I've updated my blog post from earlier in the year for those who may
not be familiar on the process:
* http://www.paul-moore.com/blog/d/2017/07/kernel-repo-process.html
--
paul moore
www.paul-moore.com
paul moore
www.paul-moore.com