[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fd7a2ab6-3fd3-e967-1959-04a828331884@web.de>
Date: Sun, 6 Oct 2019 09:00:40 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Julia Lawall <julia.lawall@...6.fr>,
YueHaibing <yuehaibing@...wei.com>, cocci@...teme.lip6.fr,
kernel-janitors@...r.kernel.org
Cc: Gilles Muller <Gilles.Muller@...6.fr>,
Nicolas Palix <nicolas.palix@...g.fr>,
Michal Marek <michal.lkml@...kovi.net>,
Matthias Männich <maennich@...gle.com>,
Jessica Yu <jeyu@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
linux-kernel@...r.kernel.org
Subject: Re: scripts: add_namespace: Fix coccicheck failed
>> I would find a commit subject like “scripts: add_namespace:
>> Add support for the default coccicheck operation mode” more appropriate
>> (if this software development will be clarified further in the shown direction
>> at all).
>
> Please let this go.
This will not happen for a while.
> Please stop criticizing the English of others.
I am occasionally trying to provide some code review.
Chances for further improvements will eventually be lost, if you do not
get informed about corresponding update candidates.
> The message is understandable, and even more informative than what you propose.
I would appreciate the selection of a better wording also in this case.
Regards,
Markus
Powered by blists - more mailing lists