From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:52840 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S933545AbeCGQfM (ORCPT ); Wed, 7 Mar 2018 11:35:12 -0500 Received: from pps.filterd (m0098417.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w27GTOev019123 for ; Wed, 7 Mar 2018 11:35:11 -0500 Received: from e06smtp12.uk.ibm.com (e06smtp12.uk.ibm.com [195.75.94.108]) by mx0a-001b2d01.pphosted.com with ESMTP id 2gjk4e9x20-1 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=NOT) for ; Wed, 07 Mar 2018 11:35:10 -0500 Received: from localhost by e06smtp12.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 7 Mar 2018 16:35:09 -0000 Subject: Re: [PATCH 1/3 RESEND] tpm: add longer timeouts for creation commands. From: Mimi Zohar To: Jonathan Corbet Cc: James Bottomley , "Winkler, Tomas" , Jarkko Sakkinen , Jason Gunthorpe , "Usyskin, Alexander" , "linux-integrity@vger.kernel.org" , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kernel@vger.kernel.org Date: Wed, 07 Mar 2018 11:35:03 -0500 In-Reply-To: <20180307085454.2c820a13@lwn.net> References: <20180304121205.16934-1-tomas.winkler@intel.com> <20180305125642.GA3425@linux.intel.com> <5B8DA87D05A7694D9FA63FD143655C1B9422E21E@hasmsx108.ger.corp.intel.com> <20180306074932.GB3624@linux.intel.com> <5B8DA87D05A7694D9FA63FD143655C1B9422EFFE@hasmsx108.ger.corp.intel.com> <1520353933.5393.21.camel@HansenPartnership.com> <1520361396.10396.396.camel@linux.vnet.ibm.com> <20180307085454.2c820a13@lwn.net> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Message-Id: <1520440503.10396.534.camel@linux.vnet.ibm.com> Sender: linux-integrity-owner@vger.kernel.org List-ID: On Wed, 2018-03-07 at 08:54 -0700, Jonathan Corbet wrote: > On Tue, 06 Mar 2018 13:36: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. > > 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. Thanks, Jon. That sounds like a really, good idea. Some maintainers are saying to put the Changelog after the "---" so that it isn't included in the patch description. One of the reasons for including the Changelog in the patch description, is to credit people with bug fixes, important rework of the patch, etc. Do you have any thoughts on this? Mimi