linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PULL REQUEST] btrfs-progs: For next merge window
Date: Mon, 21 Oct 2019 16:55:54 +0200	[thread overview]
Message-ID: <20191021145554.GM3001@twin.jikos.cz> (raw)
In-Reply-To: <64097cbe-4c2d-2c90-f64f-b4dad84f87ed@gmx.com>

On Fri, Oct 11, 2019 at 10:07:16AM +0800, Qu Wenruo wrote:
> 
> 
> On 2019/10/11 上午12:17, David Sterba wrote:
> > On Thu, Oct 10, 2019 at 04:59:32PM +0800, Qu Wenruo wrote:
> >> This patchset can be fetched from github:
> >> https://github.com/adam900710/btrfs-progs/tree/for_next
> >> Which is based on devel branch, with the following HEAD:
> > 
> > Thanks for putting the branch together, I've been too busy with kernel
> > work so progs are lagging behind constantly.
> > 
> > The current devel branch is almost ready for a release, some patches
> > will be moved to 5.4 but I'm planning to do release by tomorrow. I can
> > pull your branch as-is to 5.4 so we have time to fix any problems.
> 
> No problem at all.
> Since I don't expect this pull get merged in the next release either.

I had to rebase the branch, all patches from you (image, check) are now
in devel. I did some fixups (error messages, coding style, changelogs)
on the way.

Next will be the patchset from Omar. The fix from Johanness regarding
zstd needs to be reworked so I'll drop it for now.

      reply	other threads:[~2019-10-21 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10  8:59 [PULL REQUEST] btrfs-progs: For next merge window Qu Wenruo
2019-10-10 16:17 ` David Sterba
2019-10-11  2:07   ` Qu Wenruo
2019-10-21 14:55     ` 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=20191021145554.GM3001@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --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 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).