From: David Howells <dhowells@redhat.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: dhowells@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
jmorris@namei.org
Subject: Re: nfsd 2.6.28 merge plans
Date: Wed, 15 Oct 2008 10:17:04 +0100 [thread overview]
Message-ID: <14531.1224062224@redhat.com> (raw)
In-Reply-To: <1224017504.8907.42.camel@localhost>
Trond Myklebust <Trond.Myklebust@netapp.com> wrote:
> I'm happy with the changes that you made after the plumbers conf, so as
> far as the NFS side of the patches is concerned, we should be close to
> ready to merge.
What I'm hoping is that JamesM will pass my creds patches to Linus in this
merge window - that way you don't need to carry them in your tree as the main
cachefiles patch requires them to deal with security.
David
next prev parent reply other threads:[~2008-10-15 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 23:22 nfsd 2.6.28 merge plans J. Bruce Fields
2008-10-14 19:07 ` Andrew Morton
2008-10-14 20:33 ` David Howells
2008-10-14 20:51 ` Trond Myklebust
2008-10-15 9:17 ` David Howells [this message]
2008-11-20 14:25 ` David Howells
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=14531.1224062224@redhat.com \
--to=dhowells@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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.