From: David Sterba <dsterba@suse.cz>
To: dsterba@suse.cz, Qu Wenruo <quwenruo.btrfs@gmx.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PULL REQUEST v2] btrfs-progs updates, the main part
Date: Fri, 26 Apr 2019 18:14:06 +0200 [thread overview]
Message-ID: <20190426161405.GU20156@twin.jikos.cz> (raw)
In-Reply-To: <20190418180304.GQ20156@twin.jikos.cz>
On Thu, Apr 18, 2019 at 08:03:04PM +0200, David Sterba wrote:
> On Tue, Apr 16, 2019 at 10:23:59AM +0800, Qu Wenruo wrote:
> > Hi David,
> >
> > Here is my pull request for the btrfs-progs:
> > https://github.com/adam900710/btrfs-progs/tree/for_devel
> >
> > The basis is the following commit from your devel branch:
> > commit cfa470d5a6b6b305fed4898b64db31c125b4dcbc (david/devel)
> > Author: Nikolay Borisov <nborisov@suse.com>
> > Date: Mon Mar 11 12:20:56 2019 +0200
> >
> > btrfs-progs: Remove get_argv0_buf
> >
> > The commit on the top is going to revert 7a12d8470e5f ("btrfs-progs: Do
> > metadata preallocation as long as we're not modifying extent tree").
> >
> > You can drop that commit if you have discarded that commit.
>
> Oh sorry, I forgot to push an updated devel without the broken patch so
> you don't have to revert it. I see how can I fix it locally so you don't
> need to resend the pull again.
The explicit revert is not a big issue so I've pulled the branch as-is.
Thanks.
prev parent reply other threads:[~2019-04-26 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 2:23 [PULL REQUEST v2] btrfs-progs updates, the main part Qu Wenruo
2019-04-18 18:03 ` David Sterba
2019-04-26 16:14 ` 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=20190426161405.GU20156@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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).