From: Krzysztof Halasa <khc@pm.waw.pl>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] checkpatch: putting the && or || on the wrong line
Date: Thu, 06 Jan 2011 21:14:48 +0000 [thread overview]
Message-ID: <m37hehloon.fsf@intrepid.localdomain> (raw)
In-Reply-To: <1294347753.12561.106.camel@Joe-Laptop> (Joe Perches's message of "Thu, 06 Jan 2011 13:02:33 -0800")
Joe Perches <joe@perches.com> writes:
>> >> Sure, standardization is a good thing - to a certain point.
>> >> We've passed this point long ago.
> Right. It's all exactly the same.
> We agree. Cites aren't necessary.
People complained on lkml and other lists that the CodingStyle /
checkpatch went way too far many times. So the evidence is there, in the
list archives, and I guess even now you're getting feedback on this.
OTOH you failed to show evidence that super-strict standardization
benefits anyone.
--
Krzysztof Halasa
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] checkpatch: putting the && or || on the wrong line
Date: Thu, 06 Jan 2011 22:14:48 +0100 [thread overview]
Message-ID: <m37hehloon.fsf@intrepid.localdomain> (raw)
In-Reply-To: <1294347753.12561.106.camel@Joe-Laptop> (Joe Perches's message of "Thu, 06 Jan 2011 13:02:33 -0800")
Joe Perches <joe@perches.com> writes:
>> >> Sure, standardization is a good thing - to a certain point.
>> >> We've passed this point long ago.
> Right. It's all exactly the same.
> We agree. Cites aren't necessary.
People complained on lkml and other lists that the CodingStyle /
checkpatch went way too far many times. So the evidence is there, in the
list archives, and I guess even now you're getting feedback on this.
OTOH you failed to show evidence that super-strict standardization
benefits anyone.
--
Krzysztof Halasa
next prev parent reply other threads:[~2011-01-06 21:14 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 5:59 [patch] checkpatch: putting the && or || on the wrong line Dan Carpenter
2011-01-04 5:59 ` Dan Carpenter
2011-01-04 6:58 ` Joe Perches
2011-01-04 6:58 ` Joe Perches
2011-01-04 9:24 ` Dan Carpenter
2011-01-04 9:24 ` Dan Carpenter
2011-01-05 10:24 ` Martin Knoblauch
2011-01-05 10:24 ` Martin Knoblauch
2011-01-04 16:38 ` J. Bruce Fields
2011-01-04 16:38 ` J. Bruce Fields
2011-01-04 16:44 ` Samuel Thibault
2011-01-04 16:44 ` Samuel Thibault
2011-01-04 17:07 ` Joe Perches
2011-01-04 17:07 ` Joe Perches
2011-01-05 17:38 ` Krzysztof Halasa
2011-01-05 17:38 ` Krzysztof Halasa
2011-01-05 17:45 ` Joe Perches
2011-01-05 17:45 ` Joe Perches
2011-01-06 12:11 ` Martin Knoblauch
2011-01-06 12:11 ` Martin Knoblauch
2011-01-06 17:43 ` Valdis.Kletnieks
2011-01-06 17:43 ` Valdis.Kletnieks
2011-01-06 12:32 ` Krzysztof Halasa
2011-01-06 12:32 ` Krzysztof Halasa
2011-01-06 17:57 ` Joe Perches
2011-01-06 17:57 ` Joe Perches
2011-01-06 20:23 ` Krzysztof Halasa
2011-01-06 20:23 ` Krzysztof Halasa
2011-01-06 21:02 ` Joe Perches
2011-01-06 21:02 ` Joe Perches
2011-01-06 21:14 ` Krzysztof Halasa [this message]
2011-01-06 21:14 ` Krzysztof Halasa
2011-01-06 21:38 ` Joe Perches
2011-01-06 21:38 ` Joe Perches
2011-01-07 17:12 ` Valdis.Kletnieks
2011-01-07 17:12 ` Valdis.Kletnieks
2011-01-08 13:42 ` Krzysztof Halasa
2011-01-08 13:42 ` Krzysztof Halasa
2011-01-08 17:12 ` Joe Perches
2011-01-08 17:12 ` Joe Perches
2011-01-06 11:55 ` Martin Knoblauch
2011-01-06 11:55 ` Martin Knoblauch
2011-01-06 12:38 ` Krzysztof Halasa
2011-01-06 12:38 ` 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=m37hehloon.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--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.