From: Valdis.Kletnieks@vt.edu
To: Joe Perches <joe@perches.com>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] checkpatch: putting the && or || on the wrong line
Date: Fri, 07 Jan 2011 17:12:32 +0000 [thread overview]
Message-ID: <26590.1294420352@localhost> (raw)
In-Reply-To: Your message of "Thu, 06 Jan 2011 13:38:38 PST." <1294349918.12561.142.camel@Joe-Laptop>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
On Thu, 06 Jan 2011 13:38:38 PST, Joe Perches said:
> http://swerl.tudelft.nl/twiki/pub/Main/TechnicalReports/TUD-SERG-2009-008.pdf
>
> RQ2 Are files or modules with a higher violation
> density more fault-prone?
>
> This holds for 10 rules in the standard, with some reserva-
> tions. There is no reliable prediction for files without ac-
> tive development (no changes) nor for files without viola-
> tions. Also, the observed relation becomes less pronounced
> in time, as the number of registered open faults decreases.
In other words, code not written to style is like finding a brown M&M
at a Van Halen concert...
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Valdis.Kletnieks@vt.edu
To: Joe Perches <joe@perches.com>
Cc: Krzysztof Halasa <khc@pm.waw.pl>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] checkpatch: putting the && or || on the wrong line
Date: Fri, 07 Jan 2011 12:12:32 -0500 [thread overview]
Message-ID: <26590.1294420352@localhost> (raw)
In-Reply-To: Your message of "Thu, 06 Jan 2011 13:38:38 PST." <1294349918.12561.142.camel@Joe-Laptop>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
On Thu, 06 Jan 2011 13:38:38 PST, Joe Perches said:
> http://swerl.tudelft.nl/twiki/pub/Main/TechnicalReports/TUD-SERG-2009-008.pdf
>
> RQ2 Are files or modules with a higher violation
> density more fault-prone?
>
> This holds for 10 rules in the standard, with some reserva-
> tions. There is no reliable prediction for files without ac-
> tive development (no changes) nor for files without viola-
> tions. Also, the observed relation becomes less pronounced
> in time, as the number of registered open faults decreases.
In other words, code not written to style is like finding a brown M&M
at a Van Halen concert...
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-01-07 17:12 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
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 [this message]
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=26590.1294420352@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=khc@pm.waw.pl \
--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.