From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Btrfs biweekly conference call
Date: Tue, 15 Jul 2008 20:53:43 +0000 [thread overview]
Message-ID: <1216155223.24425.319.camel@think.oraclecorp.com> (raw)
Hello everyone,
Starting tomorrow, we'll have public conference calls every other week
to discuss Btrfs development plans. IBM is providing the conference
call bridge (thanks Mingming)
Wednesday 10:30-11:00am (US Pacific time)
* Dial-in Number(s):
* Toll: 1-314-655-1416
* Toll Free: 1-877-422-0049
*
* Participant Pin access code: 209652
This week's call will focus on the new tree concurrency code in the
unstable tree, and other patches pending inclusion for the next release.
-chris
next reply other threads:[~2008-07-15 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 20:53 Chris Mason [this message]
2008-07-16 19:19 ` btrfs & SSD testing Ric Wheeler
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=1216155223.24425.319.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@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