From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Dean Hildebrand <seattleplus@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Linux pNFS status meeting 5/27/10
Date: Wed, 26 May 2010 14:01:09 -0400 [thread overview]
Message-ID: <1274896869.5270.18.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <4BFD5DBD.6090707@gmail.com>
On Wed, 2010-05-26 at 10:43 -0700, Dean Hildebrand wrote:
> Meeting on Thursday 5/27/2010 at 9:30 AM PDT (12:30 PM EST).
I have a conflict tomorrow. There's a NetApp all-hands meeting that is
scheduled to last until 1:00pm. I suspect that Andy, Ricardo and Fred
have the same constraint...
Cheers
Trond
next prev parent reply other threads:[~2010-05-26 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 17:43 Linux pNFS status meeting 5/27/10 Dean Hildebrand
2010-05-26 18:01 ` Trond Myklebust [this message]
[not found] ` <1274896869.5270.18.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-05-26 18:33 ` Dean Hildebrand
2010-05-27 5:10 ` Labiaga, Ricardo
2010-05-27 9:17 ` Benny Halevy
2010-05-27 13:01 ` William A. (Andy) Adamson
2010-05-27 15:17 ` Dean Hildebrand
2010-05-27 5:09 ` Labiaga, Ricardo
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=1274896869.5270.18.camel@heimdal.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=seattleplus@gmail.com \
/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).