From: Chris Mason <chris.mason@oracle.com>
To: Ameya Palande <ameya.palande@nokia.com>
Cc: ext Arjan van de Ven <arjan@linux.intel.com>,
"meego-dev@meego.com" <meego-dev@meego.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [MeeGo-dev] Btrfs as default file system
Date: Tue, 11 May 2010 09:18:44 -0400 [thread overview]
Message-ID: <20100511131844.GB27606@think> (raw)
In-Reply-To: <1273583736.2336.105.camel@sanganak>
On Tue, May 11, 2010 at 04:15:36PM +0300, Ameya Palande wrote:
> Hi Arjan,
>
> On Tue, 2010-05-11 at 15:03 +0200, ext Arjan van de Ven wrote:
> > On 5/11/2010 4:00, Ameya Palande wrote:
> > > Hi,
> > >
> > > I wanted to know why Btrfs is selected as default file system for MeeGo.
> > > Following text is copied from Btrfs kernel Kconfig option:
> > >
> > > Btrfs filesystem (EXPERIMENTAL) Unstable disk format
> >
> > the Kconfig text is out of date.
>
> Thanks for the information :)
>
> I am CCing this to linux-btrfs so that someone can take a look at this
> text and fix this for 2.6.34 release.
>
> Can someone update the btrfs kconfig text which says that this file
> system is experimental and on disk format is not yet finalized?
Hi everyone,
It is too late for such a change in 2.6.34, Linus announced the final RC
this week. But I'll have this queued in my .35 releases.
If meego would like to include a patch for this in their kernel, I'd be
happy to send it along.
-chris
next parent reply other threads:[~2010-05-11 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1273575646.2336.9.camel@sanganak>
[not found] ` <4BE95584.7000204@linux.intel.com>
[not found] ` <1273583736.2336.105.camel@sanganak>
2010-05-11 13:18 ` Chris Mason [this message]
2010-05-14 13:47 ` [MeeGo-dev] Btrfs as default file system Christian Kujau
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=20100511131844.GB27606@think \
--to=chris.mason@oracle.com \
--cc=ameya.palande@nokia.com \
--cc=arjan@linux.intel.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=meego-dev@meego.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 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.