[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=G_qnoNhjrr2K7h3u=k8AXr2QTjoN9uJ53Ls2FvsQd9w@mail.gmail.com>
Date: Fri, 9 Jun 2023 10:23:24 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Jonathan Corbet <corbet@....net>
Cc: Íñigo Huguet <ihuguet@...hat.com>,
ojeda@...nel.org, danny@...ag0n.dev, masahiroy@...nel.org,
jgg@...dia.com, mic@...ikod.net, linux-kernel@...r.kernel.org,
joe@...ches.com, linux@...musvillemoes.dk, willy@...radead.org,
mailhol.vincent@...adoo.fr
Subject: Re: [PATCH v4] Add .editorconfig file for basic formatting
On Fri, Jun 9, 2023 at 9:50 AM Jonathan Corbet <corbet@....net> wrote:
>
> So I must confess to still being really nervous about installing a file
> that will silently reconfigure the editors of everybody working on the
Yeah, especially given the variety of editors (and plugins for those)
used for kernel development.
> kernel source; I wish there were a straightforward way to do this as an
> opt-in thing. We're talking about creating a flag-day behavioral change
> for, potentially, thousands of kernel developers. Something tells me
> that we might just hear from a few of them.
>
> I wonder if we should, instead, ship a file like this as something like
> Documentation/process/editorconfig, then provide a "make editorconfig"
> command that installs it in the top-level directory for those who want
> it?
That would make me less worried indeed. It would also allow to be a
bit more aggressive on introducing some of the unclear file
extensions/rules to test them out first over time.
Cheers,
Miguel
Powered by blists - more mailing lists