From: Wolfram Sang <w.sang@pengutronix.de>
To: Joe Perches <joe@perches.com>
Cc: Fredrik Gustafsson <iveqy@iveqy.com>,
apw@canonical.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch.pl skip long lines
Date: Sun, 13 Jun 2010 07:49:32 +0200 [thread overview]
Message-ID: <20100613054932.GB17012@pengutronix.de> (raw)
In-Reply-To: <1276407372.1449.33.camel@Joe-Laptop.home>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
> > Instead of adding another command-line option, I'd suggest to just use CHK
> > instead of WARN, so this check will be enabled with --strict. I wonder if there
> > is already consensus on deprecating the 80-char-rule?
>
> Nope. There's a vocal contingent that doesn't like it though.
> An earlier thread and suggested patch below.
> http://lkml.org/lkml/2009/12/18/3
Thought so. I like your approach, missed it back then. I'd vote for 132 chars
as the next limit, though.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2010-06-13 5:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 17:09 Fredrik Gustafsson
2010-06-13 1:04 ` Wolfram Sang
2010-06-13 5:36 ` Joe Perches
2010-06-13 5:49 ` Wolfram Sang [this message]
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=20100613054932.GB17012@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=apw@canonical.com \
--cc=iveqy@iveqy.com \
--cc=joe@perches.com \
--cc=linux-kernel@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®