[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200727134411.73461df2fe73f8f96d93f75e@linux-foundation.org>
Date: Mon, 27 Jul 2020 13:44:11 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: SeongJae Park <sjpark@...zon.com>
Cc: Michał Mirosław <mirq-linux@...e.qmqm.pl>,
SeongJae Park <sj38.park@...il.com>,
Joe Perches <joe@...ches.com>, <linux-kernel@...r.kernel.org>,
<apw@...onical.com>, <colin.king@...onical.com>, <jslaby@...e.cz>,
<pavel@....cz>, SeongJae Park <sjpark@...zon.de>
Subject: Re: checkpatch: support deprecated terms checking
On Mon, 27 Jul 2020 08:54:41 +0200 SeongJae Park <sjpark@...zon.com> wrote:
> > > > Unfortunately, the inexperienced _do_ in fact run
> > > > checkpatch on files and submit inappropriate patches.
I don't think I really agree with the "new code only" guideline (where
did this come from, anyway?). 10 years from now any remaining pre-2020
terms will look exceedingly archaic and will get converted at some
point.
Wouldn't be longterm realistic to just bite the bullet now and add these
conversions to the various todo lists?
Powered by blists - more mailing lists