From: Andrew Morton <akpm@linux-foundation.org>
To: Joe Perches <joe@perches.com>
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, 1 Apr 2015 13:18:24 -0700 [thread overview]
Message-ID: <20150401131824.efafdf9c97188f97cb4a212c@linux-foundation.org> (raw)
In-Reply-To: <1427918969.31790.78.camel@perches.com>
On Wed, 01 Apr 2015 13:09:29 -0700 Joe Perches <joe@perches.com> wrote:
> On Wed, 2015-04-01 at 21:36 +0200, Jonathan Corbet wrote:
> > On Wed, 1 Apr 2015 12:20:01 -0700
> > Andrew Morton <akpm@linux-foundation.org> wrote:
> > > waah, I use 75 and this patch has ruined my life.
>
> crybaby... :)
I'm very sensitive.
> > I use 75 too, FWIW.
> >
> > It seems to me that nobody out there complains about 75-character lines
> > in commit logs; it's the 120-character lines that irritate people. I
> > would suggest that this limit could be set to 75 (or even, say, 77)
>
> 77 might be one too many.
>
> git log has a default 4 space indent of the commit message so
> 75 or 76 would still fit an 80 column screen.
That's a good point. Good enough to be in a changelog ;)
76 sounds a bit risky - I don't think I trust every output device to
dtrt with 80-column text. I might be wrong about that. 75 would save
my handkerchiefs.
next prev parent reply other threads:[~2015-04-01 20:18 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 ` Joe Perches
2015-03-31 19:06 ` 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 [this message]
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=20150401131824.efafdf9c97188f97cb4a212c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ipm@chirality.org.uk \
--cc=joe@perches.com \
--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
all inboxes | Powered by JetHome®