From: Steve Dickson <SteveD@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: BAT-Oct-15 Who's in Who's out
Date: Thu, 10 Sep 2015 17:33:08 -0400 [thread overview]
Message-ID: <55F1F714.3010300@RedHat.com> (raw)
Hello,
Just a quick reminder the deadline for hotel
registration, at the Red Hat rate, is this
Saturday Sept 12.
Note the Westford Regency Inn does have a on-call
shuttle to the Westford office for people who don't
have cars...
I've got our hardware people looking into building
a RDMA mini lab... I'm very hopeful that will happen.
I'm also looking into have an Microsoft AD available
to test against... Hopefully without changing realms
or user names.
Finally, there is a very good chance of having a
Flex Files Layout server up and running as well.
The Red Hat sponsored party will be Wed Oct 14.
6pm to 8pm... Drinks and apps as usual...
So at this point I need to know names, email address
and shirt sizes...
Any question/comments please let me know...
steved.
reply other threads:[~2015-09-10 21:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=55F1F714.3010300@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).