From: "Niklas Söderlund" <niklas.soderlund@corigine.com>
To: Joe Perches <joe@perches.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, 5 Sep 2022 12:49:00 +0200 [thread overview]
Message-ID: <YxXUHPWtyrt6kNI1@sleipner.dyn.berto.se> (raw)
In-Reply-To: <dc45a7021bb765ea34c5b9228454f255764c7bc9.camel@perches.com>
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,
The work on foo and bar introduced a bug that can be
fixed by doing baz.
I think it's for this reason other checks for tags include the ':'.
>
> > + my $tag = $1;
> > + $orig_commit = $2;
> > + $title = $3;
> > +
> > + $tag_case = 0 if $tag eq "Fixes:";
> > + $tag_space = 0 if ($line =~ /^fixes: [0-9a-f]{5,} ($balanced_parens)/i);
>
> fixes:? here too
>
> Pity there's no simple way to consolidate this git commit test block
> with the existing git id commit block.
I agree.
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2022-09-05 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 15:53 [PATCH] checkpatch: warn for non-standard fixes tag style Niklas Söderlund
2022-08-30 3:06 ` Joe Perches
2022-09-05 10:49 ` Niklas Söderlund [this message]
2022-09-05 18:00 ` Joe Perches
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=YxXUHPWtyrt6kNI1@sleipner.dyn.berto.se \
--to=niklas.soderlund@corigine.com \
--cc=apw@canonical.com \
--cc=corbet@lwn.net \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.peens@corigine.com \
--cc=lukas.bulwahn@gmail.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