[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f29db30997454e99c57b3fe0f5928b71efa484a7.camel@linux.intel.com>
Date: Sat, 10 Mar 2018 14:37:53 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Mimi Zohar <zohar@...ux.vnet.ibm.com>,
James Bottomley <James.Bottomley@...senPartnership.com>,
"Winkler, Tomas" <tomas.winkler@...el.com>
Cc: 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>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/3 RESEND] tpm: add longer timeouts for creation
commands.
On Tue, 2018-03-06 at 13:36 -0500, Mimi Zohar 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. I've seen
> Andrew Morton cut and paste the cover letter in the first patch
> description of the patch set.
When I contribute code, the cover letter helps me to do the Right
Thing.. Taking the time to write a proper cover letter helps to do a
"mental exercise" that
1. The changes make sense in the first place.
2. Only the necessary is done, not more or less.
Even for a small patch set the time used to write the cover letter
will pay off because it helps the maitainer to make a fair and
educated decision.
/Jarkko
Powered by blists - more mailing lists