From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: zohar@linux.vnet.ibm.com, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] KEYS: Keyring changes for security/next
Date: Fri, 6 May 2016 09:14:55 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1605060914320.30180@namei.org> (raw)
In-Reply-To: <13026.1462486157@warthog.procyon.org.uk>
On Thu, 5 May 2016, David Howells wrote:
> The following changes since commit 9735a22799b9214d17d3c231fe377fc852f042e9:
>
> Linux 4.6-rc2 (2016-04-03 09:09:40 -0500)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-next-20160505
>
> for you to fetch changes up to d55201ce08bfae40ae0062be126f49471a55bcad:
>
> Merge branch 'keys-trust' into keys-next (2016-05-04 17:20:20 +0100)
Pulled.
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2016-05-05 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 22:09 [GIT PULL] KEYS: Keyring changes for security/next David Howells
2016-05-05 23:14 ` 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.LRH.2.20.1605060914320.30180@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.com \
/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