From: Martin Knoblauch <spamtrap@knobisoft.de>
To: Dan Carpenter <error27@gmail.com>, Joe Perches <joe@perches.com>
Cc: Andy Whitcroft <apw@canonical.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] checkpatch: putting the && or || on the wrong line
Date: Wed, 5 Jan 2011 02:24:46 -0800 (PST) [thread overview]
Message-ID: <232289.97320.qm@web113301.mail.gq1.yahoo.com> (raw)
In-Reply-To: <20110104092431.GB1886@bicker>
----- Original Message ----
> From: Dan Carpenter <error27@gmail.com>
> To: Joe Perches <joe@perches.com>
> Cc: Andy Whitcroft <apw@canonical.com>; linux-kernel@vger.kernel.org;
>kernel-janitors@vger.kernel.org
> Sent: Tue, January 4, 2011 10:24:31 AM
> Subject: Re: [patch] checkpatch: putting the && or || on the wrong line
>
> On Mon, Jan 03, 2011 at 10:58:50PM -0800, Joe Perches wrote:
> > On Tue, 2011-01-04 at 08:59 +0300, Dan Carpenter wrote:
> > > + WARN("put the && or || at the end of the previous line\n" .
>$herecurr);
> >
> > I've submitted something like this a couple of times and gotten
> > various objections but I think it's sensible.
> >
> > https://lkml.org/lkml/2009/12/5/65
> > https://lkml.org/lkml/2010/7/11/92
>
> If everyone except you thinks it's a waste of time, then stop asking me
> to redo my patches. :/ I don't care either way so long as CodingStyle
> and checkpatch reflect the rules.
>
The problem is that CodingStyle (here and elsewhere) is viewed a the holy-grail
or at least natural-law by some. It should not. It is just about style/taste and
that will never suit everybody. Insisting to much on style is just driving those
away that:
a) just want to contribute content
b1) have their own style for decades
b2) detest uniformity
For *me* the sensible thing is to keep "style" when you make small
modifications/patches to existing stuff, but use whatever style is best for you
when contributing new stuff.
Anyway, I just wanted to say "Happy New Year" to Linux :-)
Cheers
Martin
next prev parent reply other threads:[~2011-01-05 10:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 5:59 Dan Carpenter
2011-01-04 6:58 ` Joe Perches
2011-01-04 9:24 ` Dan Carpenter
2011-01-05 10:24 ` Martin Knoblauch [this message]
2011-01-04 16:38 ` J. Bruce Fields
2011-01-04 16:44 ` Samuel Thibault
2011-01-04 17:07 ` Joe Perches
2011-01-05 17:38 ` Krzysztof Halasa
2011-01-05 17:45 ` Joe Perches
2011-01-06 12:11 ` Martin Knoblauch
2011-01-06 17:43 ` Valdis.Kletnieks
2011-01-06 12:32 ` Krzysztof Halasa
2011-01-06 17:57 ` Joe Perches
2011-01-06 20:23 ` Krzysztof Halasa
2011-01-06 21:02 ` Joe Perches
2011-01-06 21:14 ` Krzysztof Halasa
2011-01-06 21:38 ` Joe Perches
2011-01-07 17:12 ` Valdis.Kletnieks
2011-01-08 13:42 ` Krzysztof Halasa
2011-01-08 17:12 ` Joe Perches
2011-01-06 11:55 ` Martin Knoblauch
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=232289.97320.qm@web113301.mail.gq1.yahoo.com \
--to=spamtrap@knobisoft.de \
--cc=apw@canonical.com \
--cc=error27@gmail.com \
--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 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®