From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: David Miller <davem@davemloft.net>,
Ian Morris <ipm@chirality.org.uk>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: [PATCH] checkpatch/SubmittingPatches: Suggest line wrapping commit messages at 72 columns
Date: Tue, 31 Mar 2015 11:40:25 -0700 [thread overview]
Message-ID: <1427827225.18175.3.camel@perches.com> (raw)
In-Reply-To: <1427825806.10376.42.camel@perches.com>
Commit messages are sometimes overly long.
Suggest line wrapping at 72 columns.
Add a checkpatch test for long commit messages as well.
Signed-off-by: Joe Perches <joe@perches.com>
---
On Tue, 2015-03-31 at 11:16 -0700, Joe Perches wrote:
> On Tue, 2015-03-31 at 13:53 -0400, David Miller wrote:
> > From: Ian Morris <ipm@chirality.org.uk>
> > > The following patches address some coding style issues only. No
> > > functional changes and no changes detected by objdiff.
> > >
> > > The IPV6 code uses multiple different styles when comparing with
> > > NULL (I.e. x == NULL and !x as well as x != NULL and x). Generally
> > > the latter form is preferred according to checkpatch and so this
> > > changes aligns the code to this style.
> >
> > Please trim your commit message lines to 80 columns in the future.
> []
> > The only reliable way to edit and format commit log messages, so that
> > everyone sees something consistent, is to do so in a pure plain ASCII
> > text editor and use newlines to break columns at ~80 columns.
>
> I think ~72 is the preferred # as by default git commit log output
> is indented a few chars.
Documentation/SubmittingPatches | 4 ++--
scripts/checkpatch.pl | 9 +++++++++
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 447671b..c9de1c3 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -614,8 +614,8 @@ The canonical patch message body contains the following:
- An empty line.
- - The body of the explanation, which will be copied to the
- permanent changelog to describe this patch.
+ - The body of the explanation, line wrapped at 72 columns, which will
+ be copied to the permanent changelog to describe this patch.
- The "Signed-off-by:" lines, described above, which will
also go in the changelog.
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index d54a814..62a7be5 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -1898,6 +1898,7 @@ sub process {
my $in_header_lines = $file ? 0 : 1;
my $in_commit_log = 0; #Scanning lines before patch
+ my $commit_log_long_line = 0;
my $reported_maintainer_file = 0;
my $non_utf8_charset = 0;
@@ -2233,6 +2234,14 @@ sub process {
"Remove Gerrit Change-Id's before submitting upstream.\n" . $herecurr);
}
+# Check for line lengths > 72 in commit log, warn once
+ if ($in_commit_log && !$commit_log_long_line &&
+ length($line) > 72) {
+ WARN("COMMIT_LOG_LONG_LINE",
+ "Possible unwrapped commit description (prefer maximum 72 chars per line)\n" . $herecurr);
+ $commit_log_long_line = 1;
+ }
+
# Check for git id commit length and improperly formed commit descriptions
if ($in_commit_log && $line =~ /\b(c)ommit\s+([0-9a-f]{5,})/i) {
my $init_char = $1;
next prev parent reply other threads:[~2015-03-31 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 13:00 [PATCH net-next 0/2] ipv6: coding style - comparisons with NULL Ian Morris
2015-03-29 13:00 ` [PATCH net-next 1/2] ipv6: coding style: comparison for equality " Ian Morris
2015-03-29 13:00 ` [PATCH net-next 2/2] ipv6: coding style: comparison for inequality " Ian Morris
2015-03-29 17:36 ` [PATCH net-next 0/2] ipv6: coding style - comparisons " Joe Perches
2015-03-31 16:39 ` Ian Morris
2015-03-31 17:50 ` Joe Perches
2015-03-31 17:53 ` David Miller
[not found] ` <1427825806.10376.42.camel@perches.com>
2015-03-31 18:40 ` Joe Perches [this message]
2015-03-31 19:06 ` [PATCH] checkpatch/SubmittingPatches: Suggest line wrapping commit messages at 72 columns David Miller
2015-04-01 19:20 ` Andrew Morton
2015-04-01 19:28 ` Joe Perches
2015-04-01 19:36 ` Jonathan Corbet
2015-04-01 20:09 ` Joe Perches
2015-04-01 20:18 ` Andrew Morton
2015-04-01 20:33 ` [PATCH V2] checkpatch/SubmittingPatches: Suggest line wrapping commit messages at 75 columns Joe Perches
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=1427827225.18175.3.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ipm@chirality.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 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.