From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>, <clm@fb.com>
Subject: Re: Btrfs progs pre-release 3.18-rc2
Date: Tue, 23 Dec 2014 08:33:46 +0800 [thread overview]
Message-ID: <5498B86A.1020003@cn.fujitsu.com> (raw)
In-Reply-To: <20141222113745.GM27601@suse.cz>
-------- Original Message --------
Subject: Re: Btrfs progs pre-release 3.18-rc2
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Date: 2014年12月22日 19:37
> On Mon, Dec 22, 2014 at 04:17:45PM +0800, Qu Wenruo wrote:
>> I'm doing the btrfsck test framework tweaks, it will not be a big change
>> but it will change the original
>> dir hierarchy, including moving of all the binary/btrfs-image dump to
>> different dirs
>> (some dir may contains several images).
>>
>> I'm afraid it may also delay 3.18 progs release, so just info you in
>> advance.
> I think I could run the tests with rc2 codebase against the images you'd
> provide but will not merge the code changes for that release.
That's all right.
I'll send 1 or 2 small bug fix for leaf-corruption recovery for v3.18.x
base soon.
Thanks,
Qu
prev parent reply other threads:[~2014-12-23 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 18:21 Btrfs progs pre-release 3.18-rc2 David Sterba
2014-12-22 8:17 ` Qu Wenruo
2014-12-22 11:37 ` David Sterba
2014-12-23 0:33 ` Qu Wenruo [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=5498B86A.1020003@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--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