From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Sterba <dsterba@suse.com>
Cc: 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 18:50:05 +1000 [thread overview]
Message-ID: <20180814185005.7a05e8ec@canb.auug.org.au> (raw)
In-Reply-To: <cover.1534161966.git.dsterba@suse.com>
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-08-14 8:50 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 [this message]
2018-08-14 9:14 ` David Sterba
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=20180814185005.7a05e8ec@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).