From: "J. Bruce Fields" <bfields@fieldses.org>
To: Marc Eshel <eshel@almaden.ibm.com>
Cc: pnfs@linux-nfs.org, linux-nfs@vger.kernel.org
Subject: Re: [pnfs] Linux pNFS status meeting 04/29
Date: Thu, 29 Apr 2010 10:46:00 -0400 [thread overview]
Message-ID: <20100429144600.GA1654@fieldses.org> (raw)
In-Reply-To: <OF9FD7A126.8253DE0C-ON88257714.00106772-88257714.00108527@us.ibm.com>
On Wed, Apr 28, 2010 at 08:00:36PM -0700, Marc Eshel wrote:
> Meeting on Thursday 04/29/10 at 9:30 AM pacific time (12:30 PM UMICH time)
Rough agenda:
1. upstream status/merge plans (trond, bfields)
2. State of pNFS tree (bhalevy)
3. Mailing list change
4. Client
4.1. Client pNFS status
4.2. Client state management design documentation (trond)
5. Server
5.1. Todo's for minimal 4.1 server (bfields)
http://wiki.linux-nfs.org/wiki/index.php/Server_4.0_and_4.1_issues
5.2. pnfs
6. redhat status
7. bakeathon plans
- Summer in Ann Arbor
- Fall in Boston?
8. new business
--b.
next parent reply other threads:[~2010-04-30 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF9FD7A126.8253DE0C-ON88257714.00106772-88257714.00108527@us.ibm.com>
2010-04-29 14:46 ` J. Bruce Fields [this message]
2010-04-29 17:39 ` [pnfs] Linux pNFS status meeting 04/29 J. Bruce Fields
2010-04-29 18:43 ` J. Bruce Fields
2010-04-30 22:03 ` J. Bruce Fields
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=20100429144600.GA1654@fieldses.org \
--to=bfields@fieldses.org \
--cc=eshel@almaden.ibm.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pnfs@linux-nfs.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