From: Boaz Harrosh <bharrosh@panasas.com>
To: Benny Halevy <benny@tonian.com>
Cc: Benny Halevy <bhalevy@panasas.com>,
NFS list <linux-nfs@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>
Subject: Re: [PATCH RFC] pnfsd-exofs: convert to v3.1 ORE
Date: Tue, 9 Aug 2011 13:37:55 -0700 [thread overview]
Message-ID: <4E419AA3.9020507@panasas.com> (raw)
In-Reply-To: <4E419720.2080909@tonian.com>
On 08/09/2011 01:22 PM, Benny Halevy wrote:
> On 2011-08-09 22:18, Boaz Harrosh wrote:
>> Benny hi
>>
>> Please push your new tree with below patch and I will
>> send you SQUASHMES ontop of your tree. This is because
>> I'm having problems making a coherent tree, because
>> current pnfs/pnfsd-exofs branch has conflicts when
>> merging with 3.1-rc1. So your rebase should save me the
>> resolving work.
>
> Done. Thanks!
>
Great! I'll get things going ontop of that
>>
>> Thanks
>> Boaz
>>
next prev parent reply other threads:[~2011-08-09 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E416E20.2010205@panasas.com>
2011-08-09 17:30 ` [PATCH RFC] pnfsd-exofs: convert to v3.1 ORE Boaz Harrosh
2011-08-09 19:18 ` Boaz Harrosh
2011-08-09 20:22 ` Benny Halevy
2011-08-09 20:37 ` Boaz Harrosh [this message]
2011-08-09 13:25 Benny Halevy
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=4E419AA3.9020507@panasas.com \
--to=bharrosh@panasas.com \
--cc=benny@tonian.com \
--cc=bhalevy@panasas.com \
--cc=linux-nfs@vger.kernel.org \
--cc=osd-dev@open-osd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox