public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joel Schopp <jschopp@austin.ibm.com>
To: Stefani Seibold <stefani@seibold.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	apw@canonical.com, davej@redhat.com
Subject: Re: [PATCH] checkpatch.pl: remove the 80 charactes punch card limit
Date: Wed, 27 Jan 2010 12:07:01 -0600	[thread overview]
Message-ID: <4B6080C5.7020306@austin.ibm.com> (raw)
In-Reply-To: <1264597747.3607.29.camel@wall-e>


> The time of 80 characters punch card and terminals are over, so i would
> be a good thing to set the line length limit to 120. Every display today
> should be able handle this. 
>   
Nack.

While the origins of 80 character lines dates back to punchcards there 
is a reason it has survived the test of time.  Lines that go longer are 
hard to comprehend.  Either they are long themselves, in which case 
breaking them up into smaller chunks on multiple lines helps 
readability, or they are starting from deep indentation, in which case 
the function should be refactored or broken up so the logic is more 
digestable. 

  reply	other threads:[~2010-01-27 18:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 13:09 [PATCH] checkpatch.pl: remove the 80 charactes punch card limit Stefani Seibold
2010-01-27 18:07 ` Joel Schopp [this message]
2010-01-27 19:01   ` David Daney
2010-01-27 20:31     ` Joel Schopp
2010-01-27 20:42       ` David Daney
2010-01-27 21:36       ` Stefani Seibold
2010-01-28 15:54 ` Andi Kleen
2010-01-28 16:39   ` Alexander Clouter
2010-01-29  5:19     ` tytso
2010-01-29 18:49       ` Joe Perches
2010-02-01 10:53     ` Simon Farnsworth
2010-01-28 17:58   ` David Daney
2010-01-28 16:01 ` Krzysztof Halasa

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=4B6080C5.7020306@austin.ibm.com \
    --to=jschopp@austin.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@canonical.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefani@seibold.net \
    /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