From: Joe Perches <joe@perches.com>
To: "Niklas Söderlund" <niklas.soderlund@corigine.com>
Cc: Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Andy Whitcroft <apw@canonical.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
oss-drivers@corigine.com,
Simon Horman <simon.horman@corigine.com>,
Louis Peens <louis.peens@corigine.com>
Subject: Re: [PATCH] checkpatch: warn for non-standard fixes tag style
Date: Mon, 05 Sep 2022 11:00:35 -0700 [thread overview]
Message-ID: <f550b468064c61e3550b50da37138802d7e9415a.camel@perches.com> (raw)
In-Reply-To: <YxXUHPWtyrt6kNI1@sleipner.dyn.berto.se>
On Mon, 2022-09-05 at 12:49 +0200, Niklas Söderlund wrote:
> Hi Joe,
>
> Thanks for your feedback.
>
> On 2022-08-29 23:06:43 -0400, Joe Perches wrote:
> > > + if ($line =~
> > > /(fixes:)\s+([0-9a-f]{5,})\s+($balanced_parens)/i) {
> >
> > Maybe use fixes:? so the colon is not required in poorly formed uses
>
> I tried that but I think it brings more problems then it is worth. With
> that change the check would run for each line of the commit message that
> begins with the string 'fixes', not just in the tags section of the
> message. So it would warn for the commit message,
I think it's not a problem.
Look at the results of:
$ git log -100000 --no-merges --format=email --grep="^fixes" -i | \
grep -i -P -oh '^fixes:?\s*[0-9a-f]{5,}\s*..' | \
sed -r -e 's/^(fixes:?\s*)[0-9a-f]+/\1/i' | \
sort | uniq -c | sort -rn | head -20
73974 Fixes: ("
1345 Fixes: ('
399 Fixes:
246 Fixes: (A
215 Fixes: ("
172 Fixes: (c
121 Fixes: (s
114 Fixes: (d
110 Fixes: (P
98 Fixes: (i
90 Fixes: (m
86 Fixes: (n
78 Fixes: :
57 Fixes ("
51 Fixes: "n
47 Fixes: (a
46 Fixes: (t
43 fixes: ("
42 Fixes: (p
41 Fixes: ('
next prev parent reply other threads:[~2022-09-05 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 15:53 Niklas Söderlund
2022-08-30 3:06 ` Joe Perches
2022-09-05 10:49 ` Niklas Söderlund
2022-09-05 18:00 ` Joe Perches [this message]
2022-09-06 9:19 ` Niklas Söderlund
2022-08-30 3:37 ` Bagas Sanjaya
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=f550b468064c61e3550b50da37138802d7e9415a.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.peens@corigine.com \
--cc=lukas.bulwahn@gmail.com \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.com \
--cc=simon.horman@corigine.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®