From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
Benny Halevy <bhalevy@panasas.com>,
Jeff Layton <jlayton@redhat.com>,
linux-nfs@vger.kernel.org
Subject: Re: [bfields@pop.test.fieldses.org: all f08d6374 Merge branch 'nfs-for-next' into linux-next results]
Date: Thu, 23 Sep 2010 17:06:42 -0400 [thread overview]
Message-ID: <20100923210642.GD14610@fieldses.org> (raw)
In-Reply-To: <DEA83846-A762-46E8-9A5B-D55215EAA8BE@oracle.com>
> On Sep 23, 2010, at 1:29 PM, Trond Myklebust wrote:
> > Looks fine to me, and I prefer this approach to the one we have today.
> >
> > Note, however, that I've already applied commit
> > d688e11007419fd060ae74d8d952a5c4ece735aa (NFSv4.1: Fix the slotid
> > initialisation in nfs_async_rename()) to the nfs-for-2.6.37 branch.
> >
> > Are people happy with me rebasing nfs-for-2.6.37 to remove the above
> > commit, and apply this one instead?
I'm happier with incremental patches and no rebasing--I like having the
history around--but the rebase won't cause me serious practical
problems.
--b.
next prev parent reply other threads:[~2010-09-23 21:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100918171546.GA9859@fieldses.org>
[not found] ` <1284831680.2787.1.camel@heimdal.trondhjem.org>
[not found] ` <20100919184549.GD32071@fieldses.org>
[not found] ` <20100920130106.GB4580@fieldses.org>
[not found] ` <20100920131025.GC4580@fieldses.org>
[not found] ` <1285091815.30222.19.camel@heimdal.trondhjem.org>
[not found] ` <20100921111657.330e7838@corrin.poochiereds.net>
2010-09-21 19:20 ` [bfields@pop.test.fieldses.org: all f08d6374 Merge branch 'nfs-for-next' into linux-next results] J. Bruce Fields
2010-09-21 19:36 ` Trond Myklebust
2010-09-21 20:00 ` Trond Myklebust
[not found] ` <1285099232.30222.25.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-09-21 20:24 ` [bfields-btOuF8jVhiP3NsPE3w5/ayCwEArCW2h5@public.gmane.org: " J. Bruce Fields
2010-09-21 20:46 ` [bfields@pop.test.fieldses.org: " Trond Myklebust
2010-09-21 20:58 ` J. Bruce Fields
2010-09-21 21:58 ` Jeff Layton
2010-09-23 17:20 ` Benny Halevy
2010-09-23 17:29 ` Trond Myklebust
2010-09-23 18:52 ` Chuck Lever
2010-09-23 21:06 ` J. Bruce Fields [this message]
2010-09-24 13:49 ` Andy Adamson
2010-09-21 19:42 ` [bfields-btOuF8jVhiP3NsPE3w5/ayCwEArCW2h5@public.gmane.org: " J. Bruce Fields
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=20100923210642.GD14610@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=bhalevy@panasas.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--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.