From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: No Btrfs conf call today
Date: Wed, 04 Feb 2009 12:13:37 -0500 [thread overview]
Message-ID: <1233767617.20318.2.camel@think.oraclecorp.com> (raw)
Hello everyone,
I have a conflict today and won't be able to run the btrfs conf call.
So, we'll pick up the call in two weeks unless anyone has urgent issues
to talk about.
-chris
next reply other threads:[~2009-02-04 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 17:13 Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-03 18:19 No btrfs conf call today Chris Mason
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=1233767617.20318.2.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