From: Linus Torvalds <torvalds@linux-foundation.org>
To: James Morris <jmorris@namei.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
Casey Schaufler <casey@schaufler-ca.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Subject: Re: [GIT PULL] security: general updates for v4.21
Date: Fri, 28 Dec 2018 20:15:12 -0800 [thread overview]
Message-ID: <CAHk-=wh+6WrC_W7ZCjMDPaZm9SuuRjoTe8Buq123CfRvTyu0wA@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1812291505480.31477@namei.org>
On Fri, Dec 28, 2018 at 8:09 PM James Morris <jmorris@namei.org> wrote:
>
> 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.
If people really want it, maybe the merge can state that explicit
thing, as it is I'm trying to push back on empty merges that don't
explain why they even exist.
Linus
next prev parent reply other threads:[~2018-12-29 4:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 19:55 [GIT PULL] security: general updates for v4.21 James Morris
2018-12-27 20:07 ` Linus Torvalds
2018-12-29 3:11 ` James Morris
2018-12-29 3:39 ` Linus Torvalds
2018-12-29 4:09 ` James Morris
2018-12-29 4:15 ` Linus Torvalds [this message]
2018-12-29 18:34 ` Casey Schaufler
2018-12-30 2:44 ` Mimi Zohar
2019-01-07 21:45 ` James Morris
2019-01-08 21:56 ` Mimi Zohar
2018-12-27 22:05 ` pr-tracker-bot
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='CAHk-=wh+6WrC_W7ZCjMDPaZm9SuuRjoTe8Buq123CfRvTyu0wA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=casey@schaufler-ca.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.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).