From: Peter Zijlstra <peterz@infradead.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Joe Perches <joe@perches.com>, Andy Whitcroft <apw@canonical.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] checkpatch: allow single space before labels
Date: Sun, 17 Oct 2010 12:37:55 +0200 [thread overview]
Message-ID: <1287311875.1998.156.camel@laptop> (raw)
In-Reply-To: <AANLkTin6H2AbL_Kr4XCtPOr+SQRxi0tKKF3puY4gybNu@mail.gmail.com>
On Sun, 2010-10-17 at 06:30 -0400, Mike Frysinger wrote:
> On Sun, Oct 17, 2010 at 06:21, Peter Zijlstra wrote:
> > On Sun, 2010-10-17 at 04:24 -0400, Mike Frysinger wrote:
> >> feel free to extend however as long as the end result is no warnings
> >> for " foo:" ;).
> >
> > I utterly detest those indented labels and am eradicating them wherever
> > I notice them. There's really no sane reason to use them what so ever.
> > Diff can be taught not to get confused about them, see my earlier email.
>
> sure, with enough shell code thrown at a problem, you can do anything.
> the change that started these warnings was for an unrelated check.
> no one proposed warning on indented labels, nor is there any statement
> at all in the coding style on these.
>
> considering you highlighted the biggest reason (diff by default does
> not handle them properly), i think that invalidates against your "no
> sane reason" statement.
I think telling people to change their diff rules (--show-c-function
isn't default enabled either) is a lot better option than to uglify the
source. These indented labels are totally annoying when reading code.
next prev parent reply other threads:[~2010-10-17 10:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-17 8:05 [PATCH] checkpatch: allow single space before labels Mike Frysinger
2010-10-17 8:21 ` Joe Perches
2010-10-17 8:24 ` Mike Frysinger
2010-10-17 10:21 ` Peter Zijlstra
2010-10-17 10:30 ` Mike Frysinger
2010-10-17 10:37 ` Peter Zijlstra [this message]
2010-10-17 10:52 ` Mike Frysinger
2010-10-17 16:54 ` Joe Perches
2010-10-17 19:30 ` Peter Zijlstra
2010-10-17 19:38 ` Joe Perches
2010-10-17 19:49 ` Peter Zijlstra
2010-10-17 19:49 ` Mike Frysinger
2010-10-17 20:01 ` Peter Zijlstra
2010-10-17 20:26 ` Mike Frysinger
2010-10-18 14:39 ` Ted Ts'o
2010-10-18 14:54 ` Ted Ts'o
2010-10-18 14:58 ` Peter Zijlstra
2010-10-18 15:03 ` Peter Zijlstra
2010-10-18 18:21 ` Mike Frysinger
2010-10-18 18:32 ` Peter Zijlstra
2010-10-18 19:09 ` Joe Perches
2010-10-17 10:20 ` Peter Zijlstra
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=1287311875.1998.156.camel@laptop \
--to=peterz@infradead.org \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier@gentoo.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.