From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paul Moore <paul@paul-moore.com>
Cc: linux-next@vger.kernel.org, selinux@tycho.nsa.gov,
linux-audit@redhat.com
Subject: Re: Please adjust the SELinux/audit trees for linux-next
Date: Sun, 30 Jul 2017 13:00:03 +1000 [thread overview]
Message-ID: <20170730130003.46910e61@canb.auug.org.au> (raw)
In-Reply-To: <CAHC9VhQY06gE3V5hp7mD-uKSDLoVbOvGXhQiXxxrek46PF_vMg@mail.gmail.com>
Hi Paul,
On Fri, 28 Jul 2017 16:33:03 -0400 Paul Moore <paul@paul-moore.com> wrote:
>
> I have just relocated the SELinux and audit kernel trees from
> infradead.org to kernel.org, please pull from the repositories below.
> Thank you.
>
> SELinux
> * git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git next
>
> Audit
> * git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git next
I have updated these in my list.
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-07-30 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 20:33 Please adjust the SELinux/audit trees for linux-next Paul Moore
2017-07-30 3:00 ` Stephen Rothwell [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=20170730130003.46910e61@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-audit@redhat.com \
--cc=linux-next@vger.kernel.org \
--cc=paul@paul-moore.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox