From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: device delete progress
Date: Mon, 22 Sep 2014 19:23:22 +0000 (UTC) [thread overview]
Message-ID: <pan$56df9$9e600d00$eb4260de$59059f98@cox.net> (raw)
In-Reply-To: pan$c3643$3e5c01cf$cc7cb117$c2a00b4b@cox.net
Duncan posted on Mon, 22 Sep 2014 16:29:26 +0000 as excerpted:
> David Sterba posted on Mon, 22 Sep 2014 11:49:55 +0200 as excerpted:
>
>> The upcomming 3.17 release should contain all the 'new df' patches that
>> were unfortunatelly delayed. There are some minor issues to be fixed
>> but I hope it'll be ready close to the kernel 3.17 release.
>
> Will that fix my "unknown" chunk profiles too?
Never mind. I see that in the 3.16.1 announcement, which I imagine I'll
get next update.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-09-22 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 2:09 device delete progress Russell Coker
2014-09-21 8:34 ` Duncan
2014-09-22 9:49 ` David Sterba
2014-09-22 16:29 ` Duncan
2014-09-22 19:23 ` Duncan [this message]
2014-09-21 17:12 ` Chris Murphy
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='pan$56df9$9e600d00$eb4260de$59059f98@cox.net' \
--to=1i5t5.duncan@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).