From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: jmorris@namei.org
Cc: linux-integrity@vger.kernel.org
Subject: 4.17 pull request
Date: Tue, 20 Mar 2018 00:06:02 +0200 [thread overview]
Message-ID: <20180319220602.GA17000@linux.intel.com> (raw)
Hi
In order to make 4.17 pull request, could you rebase next-general
so that I can drop the security fixes from my tree?
/Jarkko
next reply other threads:[~2018-03-19 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 22:06 Jarkko Sakkinen [this message]
2018-03-20 5:58 ` 4.17 pull request James Morris
2018-03-22 14:44 ` Jarkko Sakkinen
2018-03-22 21:31 ` James Morris
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=20180319220602.GA17000@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.