From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs progs v0.18 (required for 2.6.29-rc2)
Date: Sat, 17 Jan 2009 07:18:41 -0500 [thread overview]
Message-ID: <1232194721.28343.0.camel@think.oraclecorp.com> (raw)
Hello everyone,
As mentioned in the ioctl update email, I've released btrfs v0.18. This
only includes the ioctl change and none of the patches that I've been
queuing up for testing.
If you're using 2.6.29-rc2, you'll need to update if you plan on using
btrfsctl or btrfs-vol.
-chris
next reply other threads:[~2009-01-17 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 12:18 Chris Mason [this message]
2009-01-17 14:57 ` btrfs progs v0.18 (required for 2.6.29-rc2) Gabor MICSKO
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=1232194721.28343.0.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