From: Joe Perches <joe@perches.com>
To: Jim Cromie <jim.cromie@gmail.com>, linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, apw@canonical.com,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH 2/2] checkpatch: reword long-line warning about commit-msg
Date: Thu, 07 Sep 2023 11:19:17 -0700 [thread overview]
Message-ID: <80524052652a85d2efdd3e2a01e7582baf9e545b.camel@perches.com> (raw)
In-Reply-To: <20230907174506.593889-1-jim.cromie@gmail.com>
On Thu, 2023-09-07 at 11:45 -0600, Jim Cromie wrote:
> The COMMIT_LOG_LONG_LINE warning complains about:
> 1- possible unwrapped commit description
> 2- line too long
>
> The actual test is #2, so reword it to say that 1st.
> This could reduce potential confusion for newbie users.
I don't see this as valuable.
>
> Cc: apw@canonical.com
> Cc: joe@perches.com
> Cc: Kees Cook <keescook@chromium.org>
> Signed-off-by: Jim Cromie <jim.cromie@gmail.com>
> ---
> scripts/checkpatch.pl | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 6aabcc1f66c1..6e789dc07420 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -3272,7 +3272,7 @@ sub process {
> # A Fixes:, link or signature tag line
> $commit_log_possible_stack_dump)) {
> WARN("COMMIT_LOG_LONG_LINE",
> - "Possible unwrapped commit description (prefer a maximum 75 chars per line)\n" . $herecurr);
> + "Prefer a maximum 75 chars per line (possible unwrapped commit description?)\n" . $herecurr);
> $commit_log_long_line = 1;
> }
>
next prev parent reply other threads:[~2023-09-07 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 17:45 Jim Cromie
2023-09-07 18:19 ` Joe Perches [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-08 3:30 [PATCH 0/2] checkpatch tweaks Jim Cromie
2023-08-08 3:30 ` [PATCH 2/2] checkpatch: reword long-line warning about commit-msg Jim Cromie
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=80524052652a85d2efdd3e2a01e7582baf9e545b.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=jim.cromie@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
/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®