From: Steve Dickson <SteveD@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Linux NFS status meeting 1/24/13
Date: Wed, 23 Jan 2013 11:20:47 -0500 [thread overview]
Message-ID: <51000DDF.1020300@RedHat.com> (raw)
A reminder.... There will be a status meeting tomorrow (Thur Jan 23)
Note, I've taking the 'p' off the 'NFS' in the subject line since
this meeting has become more of a general NFS community status meeting...
The general format is, Bruce will give server update, Trond will give
a client update and I will give an nfs-utils and distor update.
Then we open up the floor to any other contributors, like Andy, Benny,
Boaz, etc, who have been active in recent development efforts...
We try to keep the meeting under 30mins and very to-the-point. Meaning
subjects are quickly take off-line or on to the mailing list.
Feel free to join if this something of interest...
Time: 9:30 AM PST (12:30 PM EST)
The call in numbers are:
U.S. and Canada: (800) 451-8679
International dial-in number: (212) 729-5016
Israel Toll-Free: 1-809-462-557
Conference code: 564.272.1552
steved.
reply other threads:[~2013-01-23 16:20 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=51000DDF.1020300@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).