From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Chris Mason <chris.mason@oracle.com>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Btrfs trees for linux-next
Date: Wed, 10 Dec 2008 20:06:04 -0800 [thread overview]
Message-ID: <20081210200604.8e190b0d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081211141436.030c2d65.sfr@canb.auug.org.au>
On Thu, 11 Dec 2008 14:14:36 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Andrew,
>
> On Wed, 10 Dec 2008 21:34:56 -0500 Chris Mason <chris.mason@oracle.com> wrote:
> >
> > Just an update, while I still have a long todo list and plenty of things
> > to fix in the code, these src trees have been updated with a disk format
> > I hope to maintain compatibility with from here on. There are still
> > format changes planned, but should go in through the compat mechanisms
> > in the sources now.
> >
> > The btrfs trees are still at 2.6.28-rc5, but I just tested against
> > linux-next without problems.
>
> Do you think this is ready to be added to the end of linux-next, yet? Or
> is this more -mm material?
I'd prefer that it go into linux-next in the usual fashion. But the
first step is review..
next prev parent reply other threads:[~2008-12-11 4:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 12:18 Btrfs trees for linux-next Chris Mason
2008-12-11 2:34 ` Chris Mason
2008-12-11 3:14 ` Stephen Rothwell
2008-12-11 4:06 ` Andrew Morton [this message]
2008-12-11 5:55 ` Stephen Rothwell
2008-12-11 14:43 ` Chris Mason
2008-12-15 21:03 ` Andreas Dilger
2008-12-15 22:55 ` Kay Sievers
2008-12-16 1:37 ` Chris Mason
2008-12-16 1:39 ` Kay Sievers
2008-12-17 13:23 ` Notes on support for multiple devices for a single filesystem Christoph Hellwig
2008-12-17 14:50 ` Kay Sievers
2008-12-17 15:08 ` Christoph Hellwig
2008-12-17 15:33 ` Kay Sievers
2008-12-17 14:53 ` Chris Mason
2008-12-17 19:53 ` Andrew Morton
2008-12-17 20:58 ` Chris Mason
2008-12-17 21:20 ` Kay Sievers
2008-12-17 21:26 ` Chris Mason
2008-12-17 21:27 ` Jeff Garzik
2008-12-18 21:22 ` Bryan Henderson
2008-12-17 21:24 ` Andreas Dilger
2008-12-17 21:30 ` Jeff Garzik
2008-12-17 21:41 ` Chris Mason
2008-12-22 1:59 ` Liu Hui
2008-12-17 22:04 ` Andreas Dilger
2008-12-17 22:19 ` Dave Kleikamp
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=20081210200604.8e190b0d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.