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: Mon, 22 Dec 2014 16:17:45 +0800 [thread overview]
Message-ID: <5497D3A9.8040900@cn.fujitsu.com> (raw)
In-Reply-To: <20141219182130.GL27601@twin.jikos.cz>
-------- Original Message --------
Subject: Btrfs progs pre-release 3.18-rc2
From: David Sterba <dsterba@suse.cz>
To: <linux-btrfs@vger.kernel.org>
Date: 2014年12月20日 02:21
> Hi
>
> another step towards 3.18, the changes are limited in scope and mostly
> cleanups or docs. I'd like to see more test images for new fsck code,
> there are 2 new that I missed earlier, so they don't count.
>
> The timing with end of the year is not good so if I'm not confident
> that the release is in a good shape I'm rather going to postpone it.
> Alternatively, I can do a release on Monday and then use the following
> weeks to prepare a .1 bugfix release.
>
> Known problems: the image 013 fails
Hi david,
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.
Thanks,
Qu
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-12-22 8:17 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 [this message]
2014-12-22 11:37 ` David Sterba
2014-12-23 0:33 ` Qu Wenruo
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=5497D3A9.8040900@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.