From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Btrfs v0.17 released
Date: Mon, 12 Jan 2009 14:18:59 -0500 [thread overview]
Message-ID: <1231787939.22806.40.camel@think.oraclecorp.com> (raw)
Hello everyone,
Btrfs v0.17 is now available. For download locations you can visit:
http://btrfs.wiki.kernel.org/
The main purpose of this release was to package up a btrfs-progs.tar.gz
that corresponds to the current code in the kernel.
In general, the disk format isn't going to change unless we find a
critical bug with the old format. Every attempt will be made to
maintain backwards compatibility.
There is a long long list of fixes and improvements since v0.16. The
changelog on the wiki has a short summary.
-chris
reply other threads:[~2009-01-12 19:18 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=1231787939.22806.40.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