[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.21.1812291505480.31477@namei.org>
Date: Sat, 29 Dec 2018 15:09:42 +1100 (AEDT)
From: James Morris <jmorris@...ei.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
cc: Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
linux-security-module@...r.kernel.org,
Casey Schaufler <casey@...aufler-ca.com>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Subject: Re: [GIT PULL] security: general updates for v4.21
On Fri, 28 Dec 2018, Linus Torvalds wrote:
> On Fri, Dec 28, 2018 at 7:11 PM James Morris <jmorris@...ei.org> wrote:
> >
> > I do this every development cycle, after requests from security subsystem
> > maintainers to sync to -rc kernels.
>
> Why?
>
> A merge should have a *reason*.
Yep, I understand what you mean. I can't find the discussion from several
years ago, but developers asked to be able to work with more current
kernels, and I recall you saying that if you want to do this, merge to a
specific -rc tag at least.
I'm not personally fussed either way, and if anyone cc'd has an opinion,
please comment. Otherwise, I'll go back to merging to Linus only as
necessary.
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists