From: Steve Dickson <SteveD@redhat.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: Linux pNFS status meeting 05/09/12
Date: Wed, 09 May 2012 15:22:51 -0400 [thread overview]
Message-ID: <4FAAC40B.3000407@RedHat.com> (raw)
In-Reply-To: <4FAAB880.7090800@RedHat.com>
oops... Let me revert this... send out another one that has the correct information.... sorry about that...
steved.
On 05/09/2012 02:33 PM, Steve Dickson wrote:
>
> The call in numbers are:
>
> U.S. and Canada: (800) 451-8679
> International dial-in number: (212) 729-5016
> Israel Toll-Free: 1-809-462-557
> Conference code: 564.272.1552
>
>
> --
> 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
prev parent reply other threads:[~2012-05-09 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 18:33 Linux pNFS status meeting 05/09/12 Steve Dickson
2012-05-09 19:22 ` Steve Dickson [this message]
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=4FAAC40B.3000407@RedHat.com \
--to=steved@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 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).