[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180307085454.2c820a13@lwn.net>
Date: Wed, 7 Mar 2018 08:54:54 -0700
From: Jonathan Corbet <corbet@....net>
To: Mimi Zohar <zohar@...ux.vnet.ibm.com>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
"Winkler, Tomas" <tomas.winkler@...el.com>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.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-security-module@...r.kernel.org>, "@lwn.net,
linux-kernel@...r.kernel.org,
" <linux-kernel@...r.kernel.org>"@lwn.net
Subject: Re: [PATCH 1/3 RESEND] tpm: add longer timeouts for creation
commands.
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.
jon
Powered by blists - more mailing lists