From: Benny Halevy <bhalevy@panasas.com>
To: NFS list <linux-nfs@vger.kernel.org>
Subject: [INVITE] linux-pnfs developers meeting @ Connectathon
Date: Tue, 22 Feb 2011 17:20:01 -0800 [thread overview]
Message-ID: <4D6460C1.7020602@panasas.com> (raw)
We'll have the meeting on Thursday 2011-02-24, 5 - 6 pm
in the conference room upstairs.
(See http://www.connectathon.org/ for address)
Tentative agenda:
* Connectathon wrap up
* Submit waves 3 and 4
- contents
- status
* Plans ahead
- Wave 5 and beyond
- contents
- estimated schedule
- infrastructure needed for other layouts
- files layout extras
- advanced layout recall features
Anything else people would like to talk about?
Benny
next reply other threads:[~2011-02-23 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 1:20 Benny Halevy [this message]
2011-02-24 3:33 ` [INVITE] linux-pnfs developers meeting @ Connectathon Sandeep Joshi
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=4D6460C1.7020602@panasas.com \
--to=bhalevy@panasas.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