From: David Sterba <dsterba@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Sterba <dsterba@suse.com>,
torvalds@linux-foundation.org, clm@fb.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 4.19
Date: Tue, 14 Aug 2018 11:14:38 +0200 [thread overview]
Message-ID: <20180814091438.GD24025@twin.jikos.cz> (raw)
In-Reply-To: <20180814185005.7a05e8ec@canb.auug.org.au>
On Tue, Aug 14, 2018 at 06:50:05PM +1000, Stephen Rothwell wrote:
> Hi David,
>
> On Mon, 13 Aug 2018 14:54:07 +0200 David Sterba <dsterba@suse.com> wrote:
> >
> > There are no known pending merge conflicts with other trees. Please
> > pull, thanks.
>
> Except, presumably with what is in linux-next (which is similar, but
> not identical). :-(
>
> Please clean up your linux-next included branch.
Done, sorry. Only the pull branch is there now.
next prev parent reply other threads:[~2018-08-14 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 12:54 [GIT PULL] Btrfs updates for 4.19 David Sterba
2018-08-14 8:50 ` Stephen Rothwell
2018-08-14 9:14 ` David Sterba [this message]
2018-08-14 9:56 ` Stephen Rothwell
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=20180814091438.GD24025@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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).