From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: simo@redhat.com, keyrings@linux-nfs.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Expand keyring capacity and provide support for libkrb5
Date: Fri, 30 Aug 2013 11:20:49 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.2.02.1308301120310.9639@tundra.namei.org> (raw)
In-Reply-To: <21592.1377799564@warthog.procyon.org.uk>
On Thu, 29 Aug 2013, David Howells wrote:
> James Morris <jmorris@namei.org> wrote:
>
> > > Could you pull these patches into the security tree?
> >
> > 944 files changed, 17114 insertions(+), 9157 deletions(-)
>
> Ummm... Where did that come from? That doesn't look like what's in my
> tree...
Is your tree based on mine?
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2013-08-30 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 0:20 David Howells
2013-08-29 1:44 ` James Morris
2013-08-29 18:06 ` David Howells
2013-08-30 1:20 ` James Morris [this message]
2013-08-30 9:58 ` David Howells
2013-09-03 19:08 ` David Howells
2013-09-04 0:42 ` 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=alpine.LRH.2.02.1308301120310.9639@tundra.namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=simo@redhat.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
all inboxes | Powered by JetHome®