From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: new disk format pushed to btrfs-unstable
Date: Thu, 21 Aug 2008 16:00:11 -0400 [thread overview]
Message-ID: <1219348811.7854.71.camel@think.oraclecorp.com> (raw)
Hello everyone,
I've pulled in David's NFS changes and directory hashing change. This
means the btrfs-unstable tree now has a new disk format.
All of the critical performance and stability fixes are in the
btrfs-stable tree, without disk format changes. I'll continue putting
anything important there until the next release.
Thanks to David and Balaji Rao for getting NFS support working!
-chris
reply other threads:[~2008-08-21 20:00 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=1219348811.7854.71.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