[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZbAbmchIO8Cd5hNd@surfacebook.localdomain>
Date: Tue, 23 Jan 2024 22:03:37 +0200
From: andy.shevchenko@...il.com
To: Íñigo Huguet <ihuguet@...hat.com>
Cc: ojeda@...nel.org, danny@...ag0n.dev, masahiroy@...nel.org,
jgg@...dia.com, mic@...ikod.net, linux-kernel@...r.kernel.org,
corbet@....net, joe@...ches.com, linux@...musvillemoes.dk,
willy@...radead.org, mailhol.vincent@...adoo.fr
Subject: Re: [PATCH v4] Add .editorconfig file for basic formatting
Thu, Jun 01, 2023 at 09:53:33AM +0200, Íñigo Huguet kirjoitti:
> EditorConfig is a specification to define the most basic code formatting
> stuff, and it's supported by many editors and IDEs, either directly or
> via plugins, including VSCode/VSCodium, Vim, emacs and more.
>
> It allows to define formatting style related to indentation, charset,
> end of lines and trailing whitespaces. It also allows to apply different
> formats for different files based on wildcards, so for example it is
> possible to apply different configs to *.{c,h}, *.py and *.rs.
>
> In linux project, defining a .editorconfig might help to those people
> that work on different projects with different indentation styles, so
> they cannot define a global style. Now they will directly see the
> correct indentation on every fresh clone of the project.
>
> See https://editorconfig.org
..
> +[{*.{awk,c,dts,dtsi,dtso,h,mk,s,S},Kconfig,Makefile,Makefile.*}]
Missing Kconfig.* ?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists