From: Benny Halevy <benny@tonian.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Jim Rees <rees@umich.edu>,
linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>
Subject: Re: [PATCH] nfs-utils/blkmapd: Add complex block layout discovery and mapping daemon
Date: Fri, 23 Sep 2011 13:29:24 +0300 [thread overview]
Message-ID: <4E7C5F84.50902@tonian.com> (raw)
In-Reply-To: <4E7B901A.8060907@RedHat.com>
Steve,
I'd like to rebase my pnfs-nfs-utils tree on top of your tree
but I'd rather do it on top of an "official" release rather than
over an arbitrary tip...
When do you plan on releasing a new -rc?
Benny
On 2011-09-22 22:44, Steve Dickson wrote:
>
>
> On 09/17/2011 09:25 AM, Steve Dickson wrote:
>> Hey Jim,
>>
>> My apologies for taking so long to get to this... For some
>> reason I never added to my TODO list... That problem has
>> been resolved...
>>
>>
>> On 08/11/2011 02:20 PM, Jim Rees wrote:
>>> This daemon is required to handle upcalls from the kernel pnfs block layout
>>> driver.
>>>
>>> Signed-off-by: Jim Rees <rees@umich.edu>
> Committed with a few minor tweaks to both configure.ac
> and utils/blkmapd/Makefile.ac that we discussed.
>
> steved.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-23 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 18:20 [PATCH] nfs-utils/blkmapd: Add complex block layout discovery and mapping daemon Jim Rees
2011-08-15 7:48 ` Benny Halevy
2011-09-17 13:25 ` Steve Dickson
2011-09-17 14:52 ` Jim Rees
2011-09-19 15:19 ` Steve Dickson
2011-09-22 19:44 ` Steve Dickson
2011-09-23 10:29 ` Benny Halevy [this message]
2011-09-23 12:43 ` Steve Dickson
-- strict thread matches above, loose matches on Subject: below --
2011-09-23 12:48 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=4E7C5F84.50902@tonian.com \
--to=benny@tonian.com \
--cc=SteveD@redhat.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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.