All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Hartmayer <mhartmay@linux.ibm.com>
To: <kvm@vger.kernel.org>
Cc: "Janosch Frank" <frankja@linux.ibm.com>,
	"Nico Boehr" <nrb@linux.ibm.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Andrew Jones" <andrew.jones@linux.dev>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: [kvm-unit-tests PATCH v1] editorconfig: Add max line length setting for commit message and branch description
Date: Fri, 31 Jan 2025 12:53:07 +0100	[thread overview]
Message-ID: <20250131115307.70334-1-mhartmay@linux.ibm.com> (raw)

Add max line length setting for commit messages and branch descriptions to
the Editorconfig configuration. Use herefor the same value as used by
checkpatch [1]. See [2] for details about the file 'COMMIT_EDITMSG'.

[1] https://github.com/torvalds/linux/blob/69e858e0b8b2ea07759e995aa383e8780d9d140c/scripts/checkpatch.pl#L3270
[2] https://git-scm.com/docs/git-commit/2.46.1#Documentation/git-commit.txt-codeGITDIRCOMMITEDITMSGcode

Signed-off-by: Marc Hartmayer <mhartmay@linux.ibm.com>
---
 .editorconfig | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.editorconfig b/.editorconfig
index 46d4ac64f897..03bb16cb9442 100644
--- a/.editorconfig
+++ b/.editorconfig
@@ -13,3 +13,6 @@ insert_final_newline = true
 charset = utf-8
 indent_style = tab
 indent_size = 8
+
+[{COMMIT_EDITMSG,EDIT_DESCRIPTION}]
+max_line_length = 75

base-commit: 2e66bb4b9423970ceb6ea195bd8697733bcd9071
-- 
2.43.0


             reply	other threads:[~2025-01-31 11:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 11:53 Marc Hartmayer [this message]
2025-02-04 10:25 ` [kvm-unit-tests PATCH v1] editorconfig: Add max line length setting for commit message and branch description Nico Boehr
2025-03-05 15:15 ` Thomas Huth

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=20250131115307.70334-1-mhartmay@linux.ibm.com \
    --to=mhartmay@linux.ibm.com \
    --cc=alex.bennee@linaro.org \
    --cc=andrew.jones@linux.dev \
    --cc=frankja@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=nrb@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=thuth@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.