[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5B8DA87D05A7694D9FA63FD143655C1B9423018C@hasmsx108.ger.corp.intel.com>
Date: Wed, 7 Mar 2018 16:04:02 +0000
From: "Winkler, Tomas" <tomas.winkler@...el.com>
To: Jonathan Corbet <corbet@....net>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>
CC: James Bottomley <James.Bottomley@...senPartnership.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-security-module@...r.kernel.org\" <linux-security-module@...r.kernel.org>, "@lwn.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"\" <linux-kernel@...r.kernel.org>\"@lwn.net"
<" <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.
That's clever, but still it feels like a hack.
I've try to keep cover letters as an empty commits for that but it has to be always forced when rebasing.
Not sure git has a real user friendly support for that.
Tomas
Powered by blists - more mailing lists