From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: Fix a bug which makes unfinished fsid change unrecoverable.
Date: Thu, 21 May 2015 10:52:17 +0200 [thread overview]
Message-ID: <20150521085217.GO23255@suse.cz> (raw)
In-Reply-To: <555D41D5.10109@cn.fujitsu.com>
On Thu, May 21, 2015 at 10:24:21AM +0800, Qu Wenruo wrote:
> I didn't see this patch merged into 4.0.1.
>
> As without this patch, canceled fsid change process can't be recovered.
There are only some of the fsid patches merged, the preparatory work.
When the series looks ok up to some patch I think it's better to merge
it so you don't have to resend it again.
The commandline interface is not present yet so it's not even possible
to start the fsid change.
> I totally understand that it's not good to merge a patch into the
> already fully tested tree.
> So would you please consider add this patch to next release(even 4.1 is OK)?
Yes, that's the plan.
next prev parent reply other threads:[~2015-05-21 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 6:36 [PATCH] btrfs-progs: Fix a bug which makes unfinished fsid change unrecoverable Qu Wenruo
2015-05-21 2:24 ` Qu Wenruo
2015-05-21 8:52 ` David Sterba [this message]
2015-05-26 15:26 ` David Sterba
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=20150521085217.GO23255@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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).