From: Christoph Anton Mitterer <calestyo@scientia.net>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2] Btrfs: send, fix emission of invalid clone operations within the same file
Date: Wed, 12 Feb 2020 20:20:40 +0100 [thread overview]
Message-ID: <14deddb440625512ae490a619a37034ff1caac3b.camel@scientia.net> (raw)
In-Reply-To: <CAL3q7H5ETtr_DAjTUkrzDY6-OpDJYzSsuWbZnzpR7sDh-WXqgg@mail.gmail.com>
On Tue, 2020-02-11 at 14:46 +0000, Filipe Manana wrote:
> It's a bug fix, so yes. In fact you can check that yourself:
Thanks... actually I did check it directly in linux-stable.git ... but
it must have been merged shortly afterwards ^^
Cheers,
Chris.
prev parent reply other threads:[~2020-02-12 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 11:52 [PATCH] Btrfs: send, fix emission of invalid clone operations within the same file fdmanana
2020-01-24 13:53 ` Josef Bacik
2020-01-28 15:07 ` Filipe Manana
2020-01-28 16:21 ` David Sterba
2020-01-28 17:35 ` Filipe Manana
2020-01-29 17:09 ` [PATCH v2] " fdmanana
2020-01-30 16:31 ` David Sterba
2020-02-11 14:32 ` Christoph Anton Mitterer
2020-02-11 14:46 ` Filipe Manana
2020-02-12 19:20 ` Christoph Anton Mitterer [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=14deddb440625512ae490a619a37034ff1caac3b.camel@scientia.net \
--to=calestyo@scientia.net \
--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).