From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Nachiket Naganure <nachiketun8@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [Linux-kernel-mentees] [PATCH] Script: Checkpatch: Disables commit log length check in case of valid signature tags
Date: Sun, 26 Jul 2020 13:13:18 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.2007261310140.6195@felia> (raw)
In-Reply-To: <20200726075802.396907-1-nachiketun8@gmail.com>
Commit message is wrong.
On Sun, 26 Jul 2020, Nachiket Naganure wrote:
> Checkpatch.pl outputs warnings for commit description lines that exceed
> beyond 75 characters. Sometimes these lines might contain signature tags
> that cannot be shortened. The patch checks if the line has any valid
> signature tags and disables the warning in such a case.
>
> For instance in commit ID ac854131d984, the patch
> contains a Reported by tag line which exceeds 75 chars. And there is no
> valid way to shorten the length.
>
> To fix this, we need to check if the $line variable has any valid
> signature tags which are already stored in $signature_tags variable.
>
Read the documentation on commit messages. Think about the things you are
doing wrong in your commit message.
> Signed-off-by: Nachiket Naganure <nachiketun8@gmail.com>
> ---
> scripts/checkpatch.pl | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 197436b20288..b6d5e2a8fce8 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -2806,6 +2806,8 @@ sub process {
> # filename then :
> $line =~ /^\s*(?:Fixes:|Link:)/i ||
> # A Fixes: or Link: line
> + $line =~ /$signature_tags/ ||
> + # Checks for signature_tags
Change looks more reasonable now.
Indentation is broken.
Maybe two or three iterations on this patch and it is getting ready for
submission.
Lukas
> $commit_log_possible_stack_dump)) {
> WARN("COMMIT_LOG_LONG_LINE",
> "Possible unwrapped commit description (prefer a maximum 75 chars per line)\n" . $herecurr);
> --
> 2.25.1
>
>
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-07-26 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 7:58 [Linux-kernel-mentees] [PATCH] Script: Checkpatch: Disables commit log length check in case of valid signature tags Nachiket Naganure
2020-07-26 11:13 ` Lukas Bulwahn [this message]
2020-07-26 15:09 ` Nachiket N
2020-07-26 17:12 ` 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:
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=alpine.DEB.2.21.2007261310140.6195@felia \
--to=lukas.bulwahn@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=nachiketun8@gmail.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.