From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Btrfs is now in mainline!
Date: Fri, 09 Jan 2009 19:57:51 -0500 [thread overview]
Message-ID: <1231549071.8325.43.camel@think.oraclecorp.com> (raw)
Hello everyone,
Just a quick note that Linus merged the btrfs unstable repository into
the mainline kernel. I'll cut a new stable release of btrfs-progs on
Monday to go with it (for now the unstable repo is the best choice).
I'd like to thank everyone who contributed to the code, tested,
reviewed, documented, helped organize and otherwise helped Btrfs get as
far as it has. It wouldn't have been possible without you.
There is a lot of work to do before we can really declare Btrfs
finished, but this is a huge step forward.
Cheers,
Chris
next reply other threads:[~2009-01-10 0:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 0:57 Chris Mason [this message]
2009-01-11 1:47 ` Btrfs is now in mainline! Daniel Phillips
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=1231549071.8325.43.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@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