linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel Phillips" <phillips@google.com>
To: "Chris mason" <chris.mason@oracle.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 14:28:29 -0500	[thread overview]
Message-ID: <4d47a5d10801171128t371fb3c4y27401c156f20569@mail.gmail.com> (raw)
In-Reply-To: <200801171325.55406.chris.mason@oracle.com>

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?

Regards,

Daniel

  reply	other threads:[~2008-01-17 19:28 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 [this message]
2008-01-17 20:14     ` Chris mason
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=4d47a5d10801171128t371fb3c4y27401c156f20569@mail.gmail.com \
    --to=phillips@google.com \
    --cc=btrfs-devel@oss.oracle.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).