From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christian Brauner <christian@brauner.io>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>
Subject: Re: linux-next: manual merge of the pidfd tree with Linus' tree
Date: Wed, 22 May 2019 17:48:33 +1000 [thread overview]
Message-ID: <20190522174725.6bfd51bd@canb.auug.org.au> (raw)
In-Reply-To: <20190522055235.GC13702@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 434 bytes --]
Hi Greg,
On Wed, 22 May 2019 07:52:35 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> Sorry, you are going to get a number of these types of minor conflicts
> now. That's the problem of touching thousands of files :(
Yeah, I expected that one I saw the commits. At least is is just after
-rc1, hopefully most maintainers will start their -next branches after
today :-)
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-22 7:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 1:01 linux-next: manual merge of the pidfd tree with Linus' tree Stephen Rothwell
2019-05-22 5:52 ` Greg Kroah-Hartman
2019-05-22 7:48 ` Stephen Rothwell [this message]
2019-05-22 7:55 ` Christian Brauner
2019-05-22 8:05 ` Stephen Rothwell
2019-06-06 5:40 Stephen Rothwell
2019-06-06 5:40 ` Stephen Rothwell
2019-07-08 23:17 ` Stephen Rothwell
2019-07-01 10:35 Stephen Rothwell
2019-07-09 0:19 ` Stephen Rothwell
2019-07-04 8:44 Stephen Rothwell
2019-11-15 5:32 Stephen Rothwell
2023-07-02 23:42 Stephen Rothwell
2023-07-03 7:50 ` Christian Brauner
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=20190522174725.6bfd51bd@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=christian@brauner.io \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).