[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D7AGBYQ5T2P2.3L3HM84HUCS1V@kernel.org>
Date: Fri, 24 Jan 2025 18:42:13 +0200
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Jarkko Sakkinen" <jarkko@...nel.org>, "Khaled Elnaggar"
<khaledelnaggarlinux@...il.com>, <peterhuewe@....de>, <jgg@...pe.ca>,
<shuah@...nel.org>
Cc: <linux-kernel-mentees@...r.kernel.org>,
<linux-integrity@...r.kernel.org>, <linux-kselftest@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] selftests: tpm2: create a dedicated .gitignore
On Fri Jan 24, 2025 at 6:37 PM EET, Jarkko Sakkinen wrote:
> On Fri Jan 24, 2025 at 4:35 PM EET, Khaled Elnaggar wrote:
> > On 1/23/25 11:47 AM, Jarkko Sakkinen wrote:
> > > Why?
> >
> > Sorry I should have included v1 in the thread but I am still
> > new to the LKML process.
>
> No worries, relax, it was just a one wonder question :-)
Shortest ever commit message tutorial:
1. Problem
2. Motivation
3. Solution with explanation how it will map on addressing the problem.
Do this for every possible commit and you will get it right 99%
of time. I can admit that even today I don't always get this myself
fully right but I try my best ;-) That does not mean you could not
do better than me.
And generally, depending on subsystem tho, people usually feel more
confortable with "imperative form" rather than "science paper" form.
Example:
1. Imperative: "Check the pointer for nullness."
2. Sciency: "We must check the the pointer for nullness."
BR, Jarkko
Powered by blists - more mailing lists