All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Boeckel <me@benboeckel.net>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Franziska Naepelt <franziska.naepelt@googlemail.com>,
	keyrings@vger.kernel.org, dhowells@redhat.com,
	dwmw2@infradead.org, linux-kernel@vger.kernel.org,
	Franziska Naepelt <franziska.naepelt@gmail.com>,
	kernel test robot <lkp@intel.com>,
	Linux SPDX Licenses <linux-spdx@vger.kernel.org>,
	Linux Kernel Janitors <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH v2] certs/extract-cert: Fix checkpatch issues
Date: Tue, 6 Jun 2023 17:43:50 -0400	[thread overview]
Message-ID: <20230606214350.GA142397@farprobe> (raw)
In-Reply-To: <e44d03cf-9993-483c-b3d4-6185f5c028cc@kadam.mountain>

On Tue, Jun 06, 2023 at 18:25:24 +0300, Dan Carpenter wrote:
> I'm looking through the git log to see if it's true the imperative tense
> commit message are shorter and better and neither one of those things is
> obvious to me.
> 
> This patch had an imperative subject already so it was already kind of
> imperative.  Does every sentence have to be imperative or can you just
> add a "Fix it." to the end?

I don't know about the length argument, but it feels like it reads
better when skimming summaries with the imperative mood. The way I think
about it is that the subject should complete the phrase:

    When applied, this patch will…

The body then gives more context and description as necessary. I don't
really worry so much about the mood/tense/whatever in the body except
that I try to use the present tense for anything the patch is doing and
past for any historical context. I understand that kernel maintainers
may care a lot more about it though.

Basically, a patch, on its own, does nothing (just like a recipe). It is
only when it is applied that anything actually happens. I read it as
"`git apply`, please $summary".

--Ben

  parent reply	other threads:[~2023-06-06 21:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-01 19:05 [PATCH] certs/extract-cert: Fix checkpatch issues Franziska Naepelt
2023-06-02  2:27 ` kernel test robot
2023-06-02  3:09 ` kernel test robot
2023-06-02  8:59 ` [PATCH v2] " Franziska Naepelt
2023-06-06 12:28   ` Bagas Sanjaya
2023-06-06 13:38     ` Dan Carpenter
2023-06-06 14:51       ` Jarkko Sakkinen
2023-06-06 15:25         ` Dan Carpenter
2023-06-06 16:03           ` Jarkko Sakkinen
2023-06-06 17:59             ` Franziska Näpelt
2023-06-06 18:29               ` Dan Carpenter
2023-06-06 21:43           ` Ben Boeckel [this message]
2023-06-07 16:11             ` Jarkko Sakkinen
2023-06-09 14:01         ` Dan Carpenter
2023-06-09 15:37           ` Jarkko Sakkinen
2023-06-09 15:43             ` Jarkko Sakkinen
2023-06-06 12:38   ` Jarkko Sakkinen
2023-06-06 12:44     ` Jarkko Sakkinen
2023-06-06 12:47       ` Jarkko Sakkinen
2023-06-06 14:44     ` David Howells

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230606214350.GA142397@farprobe \
    --to=me@benboeckel.net \
    --cc=bagasdotme@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=franziska.naepelt@gmail.com \
    --cc=franziska.naepelt@googlemail.com \
    --cc=jarkko@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=lkp@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.