From: Steve Dickson <SteveD@redhat.com>
To: linux-nfs@vger.kernel.org
Subject: Linux pNFS status meeting 04/12/12
Date: Thu, 12 Apr 2012 09:57:33 -0400 [thread overview]
Message-ID: <4F86DF4D.5070208@RedHat.com> (raw)
In-Reply-To: <OFB6DA5CEF.C6895471-ON882579A4.00712ECE-882579A4.00715EC4@us.ibm.com>
Meeting on Thursday 04/12/12 at 9:30 AM PST (12:30 PM EST)
Please note the new call in number:
U.S. and Canada: (800) 451-8679
International dial-in number: (212) 729-5016
Conference code: 564.272.1552
next prev parent reply other threads:[~2012-04-12 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 22:05 Linux pNFS status meeting 02/09/12 -- NO MEETING -- Marc Eshel
2012-02-14 20:38 ` Linux pNFS status meeting 02/16/12 " Marc Eshel
2012-02-15 13:57 ` Benny Halevy
2012-02-21 19:40 ` Linux pNFS status meeting 02/23/12 " Marc Eshel
2012-04-12 13:57 ` Steve Dickson [this message]
2012-04-17 16:27 ` Linux pNFS status meeting 04/12/12 Boaz Harrosh
2012-04-17 17:05 ` Steve Dickson
2012-04-17 17:26 ` Steve Dickson
2012-04-17 17:32 ` Boaz Harrosh
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=4F86DF4D.5070208@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).