From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Stefan Richter" <stefanr@s5r6.in-berlin.de>
Cc: "Satyam Sharma" <satyam.sharma@gmail.com>,
"Jeff Garzik" <jeff@garzik.org>,
"Randy Dunlap" <randy.dunlap@oracle.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: CodingStyle: start flamewar about use of braces
Date: Wed, 9 May 2007 11:59:33 +0300 [thread overview]
Message-ID: <84144f020705090159t72ea1bd8qccc60791f3be8db@mail.gmail.com> (raw)
In-Reply-To: <4641836C.200@s5r6.in-berlin.de>
On 5/9/07, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> I don't know which form is better suited to the goal of well
> maintainable code --- the compact, easy to read, winning guideline, or
> the comprehensive norm.
Bah, it's a slippery slope. Too little guidelines and we end up people
submitting code that is "obviously" violating Linux coding standards
on the basis of that it's not forbidden by Documentation/CodingStyle.
And with too much detail, we end up with something that nobody wants
to read let alone follow. So what CodingStyle should say, really, is
that maintainers have different preference and you're usually better
off following them than fighting against them ;-).
prev parent reply other threads:[~2007-05-09 8:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705081903.l48J3AOw010373@hera.kernel.org>
2007-05-08 19:43 ` Randy Dunlap
2007-05-08 21:19 ` Jeff Garzik
2007-05-08 22:25 ` Lennart Sorensen
2007-05-08 22:50 ` Stephen Clark
2007-05-08 23:01 ` Jeff Garzik
2007-05-08 23:37 ` Satyam Sharma
2007-05-09 8:16 ` Stefan Richter
2007-05-09 8:59 ` Pekka Enberg [this message]
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=84144f020705090159t72ea1bd8qccc60791f3be8db@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=satyam.sharma@gmail.com \
--cc=stefanr@s5r6.in-berlin.de \
/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®