From: Anand Jain <anand.jain@oracle.com>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 4.20.2
Date: Tue, 26 Feb 2019 13:06:48 +0800 [thread overview]
Message-ID: <03a1aba5-3a19-25fe-de3a-d99ad32d2edd@oracle.com> (raw)
In-Reply-To: <20190225180438.4249-1-dsterba@suse.com>
https://patchwork.kernel.org/patch/10732689/
Would like to bring to your notice. Above patch is not yet integrated
for a long time. Any comments?
Thanks, Anand
On 2/26/19 2:04 AM, David Sterba wrote:
> Hi,
>
> btrfs-progs version 4.20.2 have been released. This is a quick fix of a problem
> with send/receive path checks that break some setups. As there's no proper
> fix yet, the patch that caused the regression has been reverted.
>
> Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
> Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
>
> Shortlog:
>
> David Sterba (5):
> btrfs-progs: ci: explicitly request reiserfs support for btrfs-convert
> btrfs-progs: ci: switch to newer build environment
> Revert "Btrfs-progs: fix mount point detection due to partial prefix match"
> btrfs-progs: update CHANGES for v4.20.2
> Btrfs progs v4.20.2
>
> Nikolay Borisov (1):
> btrfs-progs: Use a single tab for 'leafsize (deprecated)' row
>
next prev parent reply other threads:[~2019-02-26 5:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 18:04 Btrfs progs release 4.20.2 David Sterba
2019-02-26 5:06 ` Anand Jain [this message]
2019-02-26 6:25 ` Anand Jain
[not found] ` <CABB28CzM029Wy6q6OF65M0CUZ59Rv8RQZd6ABCfrgV=eO2t4XA@mail.gmail.com>
2019-02-26 14:37 ` Anand Jain
2019-02-27 17: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=03a1aba5-3a19-25fe-de3a-d99ad32d2edd@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--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).