From: Chris mason <chris.mason@oracle.com>
To: "Daniel Phillips" <phillips@google.com>
Cc: btrfs-devel@oss.oracle.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [Btrfs-devel] [ANNOUNCE] Btrfs v0.10 (online growing/shrinking, ext3 conversion, and more)
Date: Thu, 17 Jan 2008 15:14:41 -0500 [thread overview]
Message-ID: <200801171514.41963.chris.mason@oracle.com> (raw)
In-Reply-To: <4d47a5d10801171128t371fb3c4y27401c156f20569@mail.gmail.com>
On Thursday 17 January 2008, Daniel Phillips wrote:
> On Jan 17, 2008 1:25 PM, Chris mason <chris.mason@oracle.com> wrote:
> > So, I've put v0.11 out there. It fixes those two problems and will also
> > compile on older (2.6.18) enterprise kernels.
> >
> > v0.11 does not have any disk format changes.
>
> Hi Chris,
>
> First, massive congratulations for bringing this to fruition in such a
> short time.
>
> Now back to the regular carping: why even support older kernels?
The general answer is the backports are small and easy. I don't test them
heavily, and I don't go out of my way to make things work.
But, they do make it easier for people to try out, and to figure how to use
all these new features to solve problems. Small changes that enable more
testers are always welcome.
In general, the core parts of the kernel that btrfs uses haven't had many
interface changes since 2.6.18, so this isn't a huge deal.
-chris
next prev parent reply other threads:[~2008-01-17 20:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 15:52 [ANNOUNCE] Btrfs v0.10 (online growing/shrinking, ext3 conversion, and more) Chris Mason
2008-01-15 16:55 ` Kyle McMartin
2008-01-16 10:02 ` [Btrfs-devel] " Christian Hesse
2008-01-16 17:50 ` Simon Holm Thøgersen
2008-01-17 18:25 ` Chris mason
2008-01-17 19:28 ` Daniel Phillips
2008-01-17 20:14 ` Chris mason [this message]
2008-01-17 23:17 ` Christian Hesse
2008-01-18 13:48 ` Chris mason
2008-01-21 8:57 ` Christian Hesse
2008-01-21 9:15 ` Yan Zheng
2008-01-21 10:32 ` Christian Hesse
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=200801171514.41963.chris.mason@oracle.com \
--to=chris.mason@oracle.com \
--cc=btrfs-devel@oss.oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@google.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;
as well as URLs for NNTP newsgroup(s).