From: Joe Perches <joe@perches.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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 13:09:29 -0700 [thread overview]
Message-ID: <1427918969.31790.78.camel@perches.com> (raw)
In-Reply-To: <20150401213618.029f8c1f@lwn.net>
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 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.
> and
> still achieve its real purpose while leaving far fewer ruined lives in its
> wake.
I don't wanna be held liable for that ruination, thanks.
next prev parent reply other threads:[~2015-04-01 20:09 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 ` [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
2015-04-01 19:36 ` Jonathan Corbet
2015-04-01 20:09 ` Joe Perches [this message]
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=1427918969.31790.78.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.