From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Morris <jmorris@namei.org>
Cc: linux-integrity@vger.kernel.org
Subject: Re: 4.17 pull request
Date: Thu, 22 Mar 2018 16:44:19 +0200 [thread overview]
Message-ID: <81bb819d7e914afc75cb6c8e7d9137d188f38793.camel@linux.intel.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1803201657100.29127@namei.org>
On Tue, 2018-03-20 at 16:58 +1100, James Morris wrote:
> On Tue, 20 Mar 2018, Jarkko Sakkinen wrote:
>
> > 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?
>
> Rebase it to 4.16-rc6?
Yes, thank you, and apologies for the latency in my
response :-(
/Jarkko
next prev parent reply other threads:[~2018-03-22 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 22:06 4.17 pull request Jarkko Sakkinen
2018-03-20 5:58 ` James Morris
2018-03-22 14:44 ` Jarkko Sakkinen [this message]
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=81bb819d7e914afc75cb6c8e7d9137d188f38793.camel@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.