From: Chris Mason <chris.mason@oracle.com>
To: Steven Pratt <slpratt@austin.ibm.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Latest tree?
Date: Thu, 2 Jul 2009 14:03:21 -0400 [thread overview]
Message-ID: <20090702180321.GH9498@think> (raw)
In-Reply-To: <20090702162448.GF9498@think>
On Thu, Jul 02, 2009 at 12:24:48PM -0400, Chris Mason wrote:
> On Thu, Jul 02, 2009 at 11:11:47AM -0500, Steven Pratt wrote:
> > What is the latest experimental tree to pull from? We had an
> > experimental branch, plus the newformat and newformat2 branches. Which
> > has the very latest stuff?
>
> Right now the master branch and the newformat2 branch are the same. The
> master branch is what I ask Linus to pull from and the newformat2 branch
> is the dedicated backport of all the critical newformat fixes against
> 2.6.30.
>
> There's one bug in both branches around the nodatacow and nodatasum
> modes (both are ignored). I plan on pushing that out today.
Just a quick note, I've pushed out my current queue of fixes to both the
master and newformat2 trees. The big thing missing is Josef's work on
the free space tracking and async block group caching, but I'll pull
that in once it stabilizes.
-chris
prev parent reply other threads:[~2009-07-02 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 16:11 Latest tree? Steven Pratt
2009-07-02 16:24 ` Chris Mason
2009-07-02 18:03 ` Chris Mason [this message]
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=20090702180321.GH9498@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=slpratt@austin.ibm.com \
/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