From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 4.20.2
Date: Wed, 27 Feb 2019 18:43:45 +0100 [thread overview]
Message-ID: <20190227174345.GA31119@twin.jikos.cz> (raw)
In-Reply-To: <03a1aba5-3a19-25fe-de3a-d99ad32d2edd@oracle.com>
On Tue, Feb 26, 2019 at 01:06:48PM +0800, Anand Jain wrote:
>
>
> 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?
I'm too busy with kernel patches to don't at progs very often. For
unknown reasons the quality of incoming patches has dropped so I have to
spend way more time testing and making sure that what gets merged does
not regress.
I see the pings and tag all progs patches but otherwise need to find a
calm week so I can switch to the other codebase.
prev parent reply other threads:[~2019-02-27 17:42 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
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 [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=20190227174345.GA31119@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=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).