[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yek9UEHpS16/9ajt@alley>
Date: Thu, 20 Jan 2022 11:45:36 +0100
From: Petr Mladek <pmladek@...e.com>
To: Jani Nikula <jani.nikula@...ux.intel.com>
Cc: Lucas De Marchi <lucas.demarchi@...el.com>,
linux-kernel@...r.kernel.org, intel-gfx@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org, amd-gfx@...ts.freedesktop.org,
linux-security-module@...r.kernel.org,
nouveau@...ts.freedesktop.org, netdev@...r.kernel.org,
Alex Deucher <alexander.deucher@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Ben Skeggs <bskeggs@...hat.com>,
Christian König <christian.koenig@....com>,
Chris Wilson <chris@...is-wilson.co.uk>,
Daniel Vetter <daniel@...ll.ch>,
David Airlie <airlied@...ux.ie>,
"David S . Miller" <davem@...emloft.net>,
Emma Anholt <emma@...olt.net>, Eryk Brol <eryk.brol@....com>,
Francis Laniel <laniel_francis@...vacyrequired.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Harry Wentland <harry.wentland@....com>,
Jakub Kicinski <kuba@...nel.org>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Julia Lawall <julia.lawall@...6.fr>,
Kentaro Takeda <takedakn@...data.co.jp>,
Leo Li <sunpeng.li@....com>,
Mikita Lipski <mikita.lipski@....com>,
Rahul Lakkireddy <rahul.lakkireddy@...lsio.com>,
Raju Rangoju <rajur@...lsio.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Sakari Ailus <sakari.ailus@...ux.intel.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Vishal Kulkarni <vishal@...lsio.com>
Subject: Re: [PATCH 0/3] lib/string_helpers: Add a few string helpers
On Thu 2022-01-20 11:12:27, Jani Nikula wrote:
> On Thu, 20 Jan 2022, Petr Mladek <pmladek@...e.com> wrote:
> > The problem is not that visible with yesno() and onoff(). But as you said,
> > onoff() confliscts with variable names. And enabledisable() sucks.
> > As a result, there is a non-trivial risk of two mass changes:
>
> My point is, in the past three years we could have churned through more
> than two mass renames just fine, if needed, *if* we had just managed to
> merge something for a start!
Huh, this sound alarming.
Cosmetic changes just complicate history. They make "git blame" useless.
They also complicate backports. I know that it is not problem for
mainline. But there are supported stable branches, ...
There should be a good reason for such changes. They should not be
done light-heartedly.
Best Regards,
Petr
Powered by blists - more mailing lists