From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: masahiroy@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Danny Lin" <danny@kdrag0n.dev>,
"Íñigo Huguet" <ihuguet@redhat.com>,
"Mickaël Salaün" <mic@digikod.net>,
"Vincent Mailhol" <mailhol.vincent@wanadoo.fr>
Subject: [PATCH] .editorconfig: move to Documentation/ directory
Date: Tue, 11 Jun 2024 08:49:13 +0200 [thread overview]
Message-ID: <2024061112-kilogram-poker-bacf@gregkh> (raw)
Some editors (like the vim variants), when seeing "trim_whitespace"
decide to do just that for all of the whitespace in the file you are
saving, even if it is not on a line that you have modified. This plays
havoc with diffs and is NOT something that should be intended.
As the "only trim whitespace on modified files" is not part of the
editorconfig standard, just move the whole thing off to the
Documentation/ directory so that those that wish to use such a thing can
pick it up from there.
Cc: Danny Lin <danny@kdrag0n.dev>
Cc: Íñigo Huguet <ihuguet@redhat.com>
Cc: Mickaël Salaün <mic@digikod.net>
Cc: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Cc: Masahiro Yamada <masahiroy@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
.editorconfig => Documentation/.editorconfig | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename .editorconfig => Documentation/.editorconfig (100%)
diff --git a/.editorconfig b/Documentation/.editorconfig
similarity index 100%
rename from .editorconfig
rename to Documentation/.editorconfig
--
2.45.2
next reply other threads:[~2024-06-11 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 6:49 Greg Kroah-Hartman [this message]
2024-06-11 6:53 ` [PATCH] .editorconfig: move to Documentation/ directory Danny Lin
2024-06-11 7:26 ` Greg Kroah-Hartman
2024-06-11 7:56 ` Vincent MAILHOL
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=2024061112-kilogram-poker-bacf@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=danny@kdrag0n.dev \
--cc=ihuguet@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=masahiroy@kernel.org \
--cc=mic@digikod.net \
/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