From: Steve Dickson <SteveD@redhat.com>
To: Marc Eshel <eshel@almaden.ibm.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Linux pNFS status meeting 03/10/11
Date: Thu, 10 Mar 2011 08:37:18 -0500 [thread overview]
Message-ID: <4D78D40E.7090007@RedHat.com> (raw)
In-Reply-To: <OF5807E8ED.B1E3CA64-ON8825784F.00117ACE-8825784F.001199D5@us.ibm.com>
I will not be able to make this either...
steved.
On 03/09/2011 10:12 PM, Marc Eshel wrote:
> Meeting on Thursday 03/10/11 at 9:30 AM PST (12:30 PM EST)
>
>
> USA Toll-Free: 888-426-6840
> USA Caller Paid: 215-861-6239
>
> Israel Toll-Free: 1-809-417-783
>
> Participant Code: 8792872
> --
> 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-03-10 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 3:12 Linux pNFS status meeting 03/10/11 Marc Eshel
2011-03-10 7:15 ` Benny Halevy
2011-03-10 13:37 ` Steve Dickson [this message]
2011-03-15 23:40 ` Linux pNFS status meeting CANCELED this week Marc Eshel
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=4D78D40E.7090007@RedHat.com \
--to=steved@redhat.com \
--cc=eshel@almaden.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).