[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b0194f880b217e905a9ce571e5b86b974beaef0b.camel@perches.com>
Date: Mon, 05 Dec 2022 04:39:18 -0800
From: Joe Perches <joe@...ches.com>
To: korantwork@...il.com, apw@...onical.com, dwaipayanray1@...il.com,
lukas.bulwahn@...il.com
Cc: alexs@...nel.org, linux-kernel@...r.kernel.org,
Xinghui Li <korantli@...cent.com>
Subject: Re: [PATCH] checkpatch: Add the backport commit format check
On Mon, 2022-12-05 at 17:48 +0800, korantwork@...il.com wrote:
> From: Xinghui Li <korantli@...cent.com>
>
> The backport commit has been used to be misreported as Error
> by checkpatch.pl like this:
>
> 'ERROR: Please use git commit description style
> 'commit <12+ chars of sha1> ("<title line>")' - ie:......
> commit <sha1> upstream.
>
> total: 1 errors, 0 warnings, 8 lines checked
> '
> So, add the backport commit format check to avoid the above mistake.
nak.
I don't believe this should be an accepted style.
and
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> ERROR("GIT_COMMIT_ID",
> - "Please use git commit description style 'commit <12+ chars of sha1> (\"<title line>\")' - ie: '${init_char}ommit $id (\"$description\")'\n" . $herectx);
> + "Please use git commit description style 'commit <12+ chars of sha1> (\"<title line>\")' - ie: '${init_char}ommit $id (\"$description\")'\nor check the backport commit description format\n" . $herectx);
Output messages are only single line not multiple lines.
Powered by blists - more mailing lists