archive mirror
 help / color / mirror / Atom feed
From: Lukas Bulwahn <>
To: Ayush <>
Subject: Re: [Linux-kernel-mentees] [PATCH v2] checkpatch: handle line break between commit and hash value
Date: Sat, 12 Sep 2020 13:17:33 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2009121312370.13082@felia> (raw)
In-Reply-To: <>

On Sat, 12 Sep 2020, Ayush wrote:

> checks for proper references to other commits with
> the intended format, commit <12+ characters of SHA-1 ID> ("<commit
> message") and warns about typical mistakes. Currently, it does
> not handle the case where there is a line break between commit and the
> hash value.
> It falsely warns that the hash is not prefixed by the word commit.
> This adds new conditions to parse and identify such commits and

s/commit/commit references/

> to not report an error in such cases.

> following type of commit reference is handled:
> - commit
> f4d51dffc6c01 ("Linux 5.9-rc4")
This part above is superfluous; I do not see the added value here.
> This issue was discovered through a thorough analysis of
> errors and warnings of type GIT_COMMIT_ID on commits between v5.7 and v5.8.
> Before applying this patch, reported 342 errors of type
> GIT_COMMIT_ID. After applying patch, errors reduced to 284.

Impressive numbers of improvement if that is true and not a bug.

I am currently running my evaluation to see if I see the same numbers; I 
will get back to you.

Linux-kernel-mentees mailing list

  reply	other threads:[~2020-09-12 11:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12  9:48 [Linux-kernel-mentees] [PATCH v2] checkpatch: handle line break between commit and hash value Ayush
2020-09-12 11:17 ` Lukas Bulwahn [this message]
2020-09-12 12:42 ` Lukas Bulwahn
2020-09-12 13:34 ` Ayush
2020-09-12 14:15 ` Lukas Bulwahn
2020-09-12 15:38 ` Ayush
2020-09-12 19:37 ` Ayush
2020-09-13 11:01   ` Lukas Bulwahn
2020-09-13 12:06   ` Ayush
2020-09-13 18:09     ` Lukas Bulwahn
2020-09-13 20:53     ` Ayush
2020-09-14  5:12       ` Lukas Bulwahn
2020-09-17 14:53       ` Ayush
2020-09-17 15:17         ` Lukas Bulwahn

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:

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

  git send-email \
    --in-reply-to=alpine.DEB.2.21.2009121312370.13082@felia \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).