mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: dhowells@redhat.com, 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 10:58:56 +0100	[thread overview]
Message-ID: <20702.1377856736@warthog.procyon.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.02.1308301120310.9639@tundra.namei.org>

James Morris <jmorris@namei.org> wrote:

> Is your tree based on mine?

No.  As I said in my original email:

	If you need the patches basing on your tree instead, that can be done.

;-)

David

  parent reply	other threads:[~2013-08-30  9:59 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
2013-08-30  9:58   ` David Howells [this message]
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=20702.1377856736@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=jmorris@namei.org \
    --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®