linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris mason <chris.mason@oracle.com>
To: btrfs-devel@oss.oracle.com
Cc: 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 13:25:55 -0500	[thread overview]
Message-ID: <200801171325.55406.chris.mason@oracle.com> (raw)
In-Reply-To: <20080115105238.4fc3e992@think.oraclecorp.com>

On Tuesday 15 January 2008, Chris Mason wrote:
> Hello everyone,
>
> Btrfs v0.10 is now available for download from:
>
> http://oss.oracle.com/projects/btrfs/

Well, it turns out this release had a few small problems:

* data=ordered deadlock on older kernels (including 2.6.23)
* Compile problems when ACLs were not enabled in the kernel

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.

-chris



  parent reply	other threads:[~2008-01-17 18:27 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 [this message]
2008-01-17 19:28   ` Daniel Phillips
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=200801171325.55406.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 \
    /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).