From: Paul Moore <pmoore@redhat.com>
To: selinux@tycho.nsa.gov
Subject: Re: [GIT PULL] SELinux patches for 4.4
Date: Wed, 21 Oct 2015 17:59:43 -0400 [thread overview]
Message-ID: <1915624.B5IT58XOGq@sifl> (raw)
In-Reply-To: <2506963.zmKhoxexGn@sifl>
On Wednesday, October 21, 2015 05:57:27 PM Paul Moore wrote:
> Hi James,
>
> Nine SELinux patches in total for v4.4 ...
Just a FYI, I've rebased the selinux#next and selinux#upstream branches; my
apologies if this causes anyone some extra headache, but I need to keep the
SELinux tree fairly close to James' LSM tree since he doesn't like to do any
merging.
--
paul moore
security @ redhat
next prev parent reply other threads:[~2015-10-21 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 21:57 [GIT PULL] SELinux patches for 4.4 Paul Moore
2015-10-21 21:59 ` Paul Moore [this message]
2015-10-21 23:56 ` James Morris
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=1915624.B5IT58XOGq@sifl \
--to=pmoore@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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.