[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b934b12940ab50218be3b7c5d1b98f5d4f24a1fd.camel@perches.com>
Date: Sun, 08 Mar 2020 12:44:44 -0700
From: Joe Perches <joe@...ches.com>
To: "Gustavo A. R. Silva" <gustavo@...eddedor.com>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Cc: clang-built-linux@...glegroups.com
Subject: Re: [PATCH] cvt_fallthrough: A tool to convert /* fallthrough */
comments to fallthrough;
On Sun, 2020-03-08 at 14:14 -0500, Gustavo A. R. Silva wrote:
>
> On 3/8/20 03:58, Joe Perches wrote:
> > On Sun, 2020-03-08 at 01:11 -0600, Gustavo A. R. Silva wrote:
> > > On 3/8/20 01:02, Joe Perches wrote:
> > > > > or if you are suggesting that
> > > > > the maintainers will have the predisposition of applying
> > > > > patches that will modify their coding style and then go and
> > > > > willingly fix that. I doubt the latter, though.
> > > >
> > > > If any do actually use the script, I guess we'll see.
> > > >
> > > Yep. In the meantime is a NACK from me for this version
> > > of your patch.
> >
> > Generic code reformatters of comments to code are not
> > particularly common.
> >
>
> It's no a matter of
> reformatting something. It's the opposite, it's a matter of
> not messing (removing existing blank lines) with the current
> format and merely focusing on replacing comments.
You are not correct in your assumption.
This is precisely reformatting of comments to code.
Nor are you correct in what appears to be your
general point. It's quite fine to reformat comments
for consistency.
Powered by blists - more mailing lists