All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	apw@shadowen.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] checkpatch: relax spacing and line length
Date: Sun, 06 Apr 2008 14:52:42 +0300	[thread overview]
Message-ID: <47F8B98A.1020704@panasas.com> (raw)
In-Reply-To: <20080405221822.376f0018.akpm@linux-foundation.org>

On Apr. 06, 2008, 8:18 +0300, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Sun, 6 Apr 2008 06:54:54 +0200 (CEST) Jan Engelhardt <jengelh@computergmbh.de> wrote:
> 
>>      We all had the arguments about 80 columns, so here goes a relax.
>>      Checking for 95 (or perhaps something better?), but of course we
>>      print "80" in the output, because if you happened to get to 95, it's
>>      "really time" to break it.
> 
> This will reduce the usefulness of checkpatch for those developers who
> choose to observe an 80-column limit.
> 
>>      This also relaxes the tab doctrine, because spaces DO make sense --
>>      especially when you view the code with a tab setting of not-8.
> 
> Non-tab-using code inevitably ends up having a mix of tabs and non-tabs
> and looks a mess if tabstops are set to anything other than eight.

I humbly disagree.  If you use tabs for (logical) indentation and then trailing
spaces for (graphical) alignment, not just a random mix of tabs and spaces the
code looks fine with 8-character wide tabs or any other setup.  Only when you
use tabs for graphical alignment, below fixed-width characters on the line above
you marry yourself with a specific tab expansion width.

Benny

> 
> God I wish I had not been cc'ed on this.

The idea is *not* to open the flood gates, just to allow for a bit more
flexibility to accommodate for a more robust indentation style.

> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2008-04-06 11:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06  4:54 [patch] checkpatch: relax spacing and line length Jan Engelhardt
2008-04-06  5:18 ` Andrew Morton
2008-04-06 11:52   ` Benny Halevy [this message]
2008-04-06 18:52     ` Joe Perches
2008-04-07  9:51       ` Boaz Harrosh
2008-04-06 10:08 ` Adrian Bunk
2008-04-06 11:08   ` Sam Ravnborg
2008-04-07 16:37     ` Benny Halevy
2008-04-08 17:12 ` Andy Whitcroft
2008-04-08 18:01   ` Andi Kleen
2008-04-09  8:19     ` Andy Whitcroft
2008-04-09  8:30       ` Andy Whitcroft
2008-04-09  8:46         ` Andi Kleen
2008-04-09 13:14           ` Andy Whitcroft
2008-04-09 13:18             ` Jan Engelhardt
2008-04-09 13:58               ` Andy Whitcroft
2008-04-09 16:53                 ` Andrew Morton
2008-04-09 17:43                   ` Andi Kleen
2008-04-09 20:07                   ` Andy Whitcroft
2008-04-11 15:54                     ` Andy Whitcroft
2008-04-09 15:14             ` Randy Dunlap
2008-04-09 12:10   ` Benny Halevy
2008-04-09 12:19   ` Benny Halevy
2008-04-09 13:25     ` Andy Whitcroft
2008-04-09 17:02       ` Benny Halevy
2008-04-09 17:27         ` Stefan Richter
2008-04-09 20:16         ` Andy Whitcroft
2008-04-10 23:52         ` SL Baur
2008-04-11  4:24           ` Jan Engelhardt
2008-04-12  0:26         ` Al Viro
2008-04-13  9:53           ` Benny Halevy
2008-04-13 15:18             ` Al Viro
2008-04-15  9:09               ` Benny Halevy

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=47F8B98A.1020704@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=jengelh@computergmbh.de \
    --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 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.