[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4112ab7e-1f06-d880-e471-084c78bc84d4@web.de>
Date: Wed, 29 Apr 2020 19:40:21 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Wang YanQing <udknight@...il.com>, Joe Perches <joe@...ches.com>,
Andy Whitcroft <apw@...onical.com>,
kernel-janitors@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Matteo Croce <mcroce@...hat.com>
Subject: Re: [PATCH] checkpatch: add support to check 'Fixes:' tag format
> “...
> Do not split the tag across multiple
> lines, tags are exempt from the "wrap at 75 columns" rule in order to simplify
> parsing scripts
> ...”
Why do you not like the reformatting of the quotation so far
(if such change descriptions should cope also with specific
Unicode characters)?
“…
Do not split the tag across multiple lines, tags are exempt from
the "wrap at 75 columns" rule in order to simplify parsing scripts.
…”
> And there is no sanity check for 'Fixes:' tag format in checkpatch the same
> as GIT_COMMIT_ID for git commit description, so let's expand the GIT_COMMIT_ID
> to add 'Fixes:' tag format check support.
I have got the impression that this wording might need another bit
of fine-tuning.
> + "Please use git commit description style '$prefix <12+ chars of sha1> (\"<$title>\")' - ie: '${init_char}" . substr($prefix, 1) . " $id (\"$description\")'\n" . $herecurr);
I imagine that the support for different quotation characters
can become helpful, can't it?
Regards,
Markus
Powered by blists - more mailing lists