All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Christoph Hellwig <hch@lst.de>, Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: fix dev-replace after the scrub rework
Date: Thu, 1 Jun 2023 12:22:17 +0200	[thread overview]
Message-ID: <20230601102217.GA10149@lst.de> (raw)
In-Reply-To: <bbd57e3d-c61d-cf1e-6f8c-386c24625a69@gmx.com>

On Thu, Jun 01, 2023 at 06:12:12PM +0800, Qu Wenruo wrote:
> Yes, the cleanup is also in my mind, but currently I prefer to do the
> fix first in-place, then you can do the tide up after the more critical fix.

There isn't really much of a difference in the diffstat between
doing the consolidation and duplicating everything.  So I don't
think that's much of an argument.

  reply	other threads:[~2023-06-01 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01  9:10 [PATCH] btrfs: fix dev-replace after the scrub rework Qu Wenruo
2023-06-01  9:37 ` Christoph Hellwig
2023-06-01 10:12   ` Qu Wenruo
2023-06-01 10:22     ` Christoph Hellwig [this message]
2023-06-01 10:34       ` 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=20230601102217.GA10149@lst.de \
    --to=hch@lst.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=wqu@suse.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 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.