From: Dzmitry Sankouski <dsankouski@gmail.com>
To: u-boot@lists.denx.de
Cc: Dzmitry Sankouski <dsankouski@gmail.com>
Subject: [PATCH 0/1] introduce .editorconfig
Date: Tue, 28 Feb 2023 11:45:45 +0300 [thread overview]
Message-ID: <20230228084546.1702171-1-dsankouski@gmail.com> (raw)
Current process of sending patches includes running checkpatch.pl
script for each patch, and fixing found style problems.
Editorconfig may help to prevent some style related problems
(like spaces vs tab indentation) on the fly.
Dzmitry Sankouski (1):
editorconfig: introduce .editorconfig
.editorconfig | 19 +++++++++++++++++++
.gitignore | 1 +
2 files changed, 20 insertions(+)
create mode 100644 .editorconfig
--
2.30.2
next reply other threads:[~2023-02-28 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 8:45 Dzmitry Sankouski [this message]
2023-02-28 8:45 ` [PATCH 1/1] editorconfig: introduce .editorconfig Dzmitry Sankouski
2023-02-28 15:10 ` Simon Glass
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=20230228084546.1702171-1-dsankouski@gmail.com \
--to=dsankouski@gmail.com \
--cc=u-boot@lists.denx.de \
/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