From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@kernel.org>
Cc: dsterba@suse.cz, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: fix cloning range with a hole when using the NO_HOLES feature
Date: Thu, 5 Dec 2019 14:45:52 +0100 [thread overview]
Message-ID: <20191205134551.GN2734@twin.jikos.cz> (raw)
In-Reply-To: <CAL3q7H4OK9nXTi9B5MOo59+AD0e_=OdiiV-YRZU2fV6ZO8p48Q@mail.gmail.com>
On Thu, Dec 05, 2019 at 11:22:57AM +0000, Filipe Manana wrote:
> On Mon, Nov 25, 2019 at 1:46 PM David Sterba <dsterba@suse.cz> wrote:
> >
> > On Tue, Nov 19, 2019 at 12:07:32PM +0000, fdmanana@kernel.org wrote:
> > > From: Filipe Manana <fdmanana@suse.com>
> > [...]
> >
> > Added to misc-next, thanks.
>
> I have an updated version for this. Do you prefer me to send a new
> patch version, an incremental full patch or just the diff and then
> fold it?
I think sending v2 of the patch is easier for you. Thanks.
next prev parent reply other threads:[~2019-12-05 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 12:07 [PATCH] Btrfs: fix cloning range with a hole when using the NO_HOLES feature fdmanana
2019-11-25 13:46 ` David Sterba
2019-12-05 11:22 ` Filipe Manana
2019-12-05 13:45 ` David Sterba [this message]
2019-12-05 16:57 ` [PATCH v2] " fdmanana
2019-12-06 15:43 ` 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=20191205134551.GN2734@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--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).