From: Daniel Pocock <daniel@pocock.com.au>
To: Milko Krachounov <sombre@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Will we get btrfsck by the end of the year?
Date: Sun, 01 Jan 2012 19:52:20 +0100 [thread overview]
Message-ID: <4F00AB64.40001@pocock.com.au> (raw)
In-Reply-To: <201201010048.07818.sombre@gmail.com>
On 31/12/11 23:48, Milko Krachounov wrote:
> So, is btrfsck going to be released by the end of 2011?
Doesn't seem so...
What is the next big date?
Debian 7 will probably be `frozen' within the next few months - if
btrfsck is available in time, maybe they will be able to offer btrfs as
a default root FS? If not, it could be another 2 years until Debian 8
One web site is quoting Red Hat with a 2013 release date: "RHEL 7 is two
plus years out, which from an upstream perspective is pretty darn
close," Ron Pacheco, Senior Director of Product Management at Red Hat
told InternetNews.com " - hopefully the btrfsck release isn't going to
be on that sort of timescale though?
prev parent reply other threads:[~2012-01-01 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 22:48 Will we get btrfsck by the end of the year? Milko Krachounov
2012-01-01 18:52 ` Daniel Pocock [this message]
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=4F00AB64.40001@pocock.com.au \
--to=daniel@pocock.com.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=sombre@gmail.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).