From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "Mateusz Guzik" <mjguzik@gmail.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Íñigo Huguet" <ihuguet@redhat.com>,
"Vincent MAILHOL" <mailhol.vincent@wanadoo.fr>,
"Jonathan Corbet" <corbet@lwn.net>,
ojeda@kernel.org, danny@kdrag0n.dev, mic@digikod.net,
linux-kernel@vger.kernel.org, joe@perches.com,
linux@rasmusvillemoes.dk, willy@infradead.org
Subject: Re: [PATCH v4] Add .editorconfig file for basic formatting
Date: Tue, 11 Jun 2024 08:44:40 +0200 [thread overview]
Message-ID: <2024061159-armless-conductor-3cd1@gregkh> (raw)
In-Reply-To: <20240603121853.GA19897@nvidia.com>
On Mon, Jun 03, 2024 at 09:18:53AM -0300, Jason Gunthorpe wrote:
> On Sun, Jun 02, 2024 at 05:30:51PM +0200, Mateusz Guzik wrote:
>
> > As is I think the config mostly gets in the way and most people have a
> > setup which does not use it (for example my vim does not). Alternatively
> > maye it is neovim which is overzalous here and other editors don't treat
> > the entire file. If there is a way to convince the thing to only tend to
> > whitespace issues in edited lines that would be great.
>
> Yes, I think that is quite overzealous, I'd view it as a vim issue.
What? No, vim is doing exactly what it is asked for here, it "trims all
whitespace" when saving the file.
I too just ran into this today, and it's a pain. This needs to be
fixed, sorry.
greg k-h
next prev parent reply other threads:[~2024-06-11 6:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 7:53 [PATCH v4] Add .editorconfig file for basic formatting Íñigo Huguet
2023-06-02 15:37 ` Mickaël Salaün
2023-06-04 20:49 ` Miguel Ojeda
2023-06-09 7:50 ` Jonathan Corbet
2023-06-09 8:23 ` Miguel Ojeda
2023-06-09 8:49 ` Íñigo Huguet
2023-06-09 8:50 ` Íñigo Huguet
2023-06-09 10:49 ` Miguel Ojeda
2023-06-14 11:33 ` Íñigo Huguet
2023-06-09 13:23 ` Mickaël Salaün
2023-06-14 11:40 ` Íñigo Huguet
2023-06-14 12:08 ` Rasmus Villemoes
2023-06-14 12:53 ` Vincent MAILHOL
2023-06-14 13:04 ` Íñigo Huguet
2023-06-15 2:40 ` Vincent MAILHOL
2023-06-15 6:35 ` Íñigo Huguet
2023-10-11 7:36 ` Vincent MAILHOL
2023-10-23 2:28 ` Jonathan Corbet
2023-10-23 6:18 ` Vincent MAILHOL
2023-10-23 6:26 ` Íñigo Huguet
2023-12-11 17:50 ` Masahiro Yamada
2024-06-02 15:30 ` Mateusz Guzik
2024-06-02 16:28 ` Miguel Ojeda
2024-06-02 18:17 ` Joe Perches
2024-06-03 12:18 ` Jason Gunthorpe
2024-06-03 12:52 ` Mateusz Guzik
2024-06-03 13:38 ` Miguel Ojeda
2024-06-03 15:09 ` Mateusz Guzik
2024-06-11 6:44 ` Greg KH [this message]
2024-01-23 20:03 ` andy.shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024061159-armless-conductor-3cd1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=danny@kdrag0n.dev \
--cc=ihuguet@redhat.com \
--cc=jgg@nvidia.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mailhol.vincent@wanadoo.fr \
--cc=masahiroy@kernel.org \
--cc=mic@digikod.net \
--cc=mjguzik@gmail.com \
--cc=ojeda@kernel.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox