[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3922f20fc01b7c5f555b92db5a128ee3a2d5cc12.camel@linux.intel.com>
Date: Sat, 10 Mar 2018 14:44:01 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Jonathan Corbet <corbet@....net>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
"Winkler, Tomas" <tomas.winkler@...el.com>,
Jason Gunthorpe <jgg@...pe.ca>,
"Usyskin, Alexander" <alexander.usyskin@...el.com>,
"linux-integrity@...r.kernel.org" <linux-integrity@...r.kernel.org>,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3 RESEND] tpm: add longer timeouts for creation
commands.
On Wed, 2018-03-07 at 08:54 -0700, Jonathan Corbet wrote:
> On Tue, 06 Mar 2018 13:36:36 -0500
> Mimi Zohar <zohar@...ux.vnet.ibm.com> wrote:
>
> > I've heard that some maintainers are moving away from cover letters,
> > since they are not include in the git repo and are lost.
>
> If I get a patch series with a cover letter that should be preserved, I
> apply the series in a branch then do a no-ff merge; the cover letter can
> then go into the merge commit. There's no reason why cover letters need to
> be lost.
That is an awesome idea. I'll start using this approach. Thank you.
/Jarkko
Powered by blists - more mailing lists