From: Joe Perches <joe@perches.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
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: Re: [PATCH] checkpatch/SubmittingPatches: Suggest line wrapping commit messages at 72 columns
Date: Wed, 01 Apr 2015 12:28:46 -0700 [thread overview]
Message-ID: <1427916526.31790.69.camel@perches.com> (raw)
In-Reply-To: <20150401122001.f0203b0ddac348db14e5822a@linux-foundation.org>
On Wed, 2015-04-01 at 12:20 -0700, Andrew Morton wrote:
> On Tue, 31 Mar 2015 11:40:25 -0700 Joe Perches <joe@perches.com> wrote:
>
> > Commit messages are sometimes overly long.
> > Suggest line wrapping at 72 columns.
>
> waah, I use 75 and this patch has ruined my life.
hmm... 1/4/15 or is it 4/1/15?
> Is there some way I can disable just this check without patching
> checkpatch? I suspect a lot of people will be interested in doing
> this ;)
You could s/72/75/. I won't care.
Using "./scripts/checkpatch.pl --ignore=commit_log_long_line"
would work too.
next prev parent reply other threads:[~2015-04-01 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427634005-4313-1-git-send-email-ipm@chirality.org.uk>
[not found] ` <20150331.135338.519327316482059081.davem@davemloft.net>
[not found] ` <1427825806.10376.42.camel@perches.com>
2015-03-31 18:40 ` [PATCH] checkpatch/SubmittingPatches: Suggest line wrapping commit messages at 72 columns Joe Perches
2015-03-31 19:06 ` David Miller
2015-04-01 19:20 ` Andrew Morton
2015-04-01 19:28 ` Joe Perches [this message]
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=1427916526.31790.69.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox