From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-unstable updates
Date: Tue, 24 Mar 2009 17:03:22 -0400 [thread overview]
Message-ID: <1237928602.5633.25.camel@think.oraclecorp.com> (raw)
Hello everyone,
The experimental branch is proving pretty stable, and growing important
fixes, so I've rebased those commits on top of 2.6.29 into the master
branch. These aren't quite ready for sending to Linus, but pretty
close.
I'll also pull in fixes the mailing list has collected for the master
branch.
I've put all of my locking work into the experimental branch, along with
some cleanups from Josef. This stuff is still pretty dangerous, but
they make a very big difference on lock contention.
-chris
reply other threads:[~2009-03-24 21:03 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=1237928602.5633.25.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