From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Michael Frank <mhf@linuxmail.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH, RFC: Version 2 of 2.6 Codingstyle
Date: Fri, 13 Feb 2004 14:38:21 -0800 [thread overview]
Message-ID: <20040213143821.663edcae.rddunlap@osdl.org> (raw)
In-Reply-To: <200402131638.17800.mhf@linuxmail.org>
On Fri, 13 Feb 2004 16:49:30 +0800 Michael Frank <mhf@linuxmail.org> wrote:
| --- Documentation/CodingStyle.mhf.orig.1 2004-02-13 06:05:11.000000000 +0800
| +++ Documentation/CodingStyle 2004-02-13 16:42:07.000000000 +0800
|
| Chapter 2: Breaking long lines and strings
|
| -
| -Long strings are broken into smaller strings too.
| +Descendant's are always shorter than the parent and are placed substantially
* Descendants (plural, not possessive)
| +to the right. The same applies to function headers with a long argument list.
| +Long strings are as well broken into smaller strings.
| +4) forgetting about sideeffects. Macros defining expressions must enclose the
* <sideeffects> : it's still not one word.
| +expression in parenthesis. Note that this does not eliminate all side effects.
* parentheses
--
~Randy
next prev parent reply other threads:[~2004-02-13 22:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 22:15 PATCH, RFC: 2.6 Documentation/Codingstyle Michael Frank
2004-02-12 23:20 ` Tim Bird
2004-02-12 23:46 ` Måns Rullgård
2004-02-13 0:19 ` Tim Hockin
2004-02-12 23:38 ` Randy.Dunlap
2004-02-13 1:50 ` Alex Goddard
2004-02-13 1:52 ` Maciej Zenczykowski
2004-02-13 0:13 ` viro
2004-02-13 1:12 ` J. Bruce Fields
2004-02-13 8:49 ` PATCH, RFC: Version 2 of 2.6 Codingstyle Michael Frank
2004-02-13 9:44 ` Andries Brouwer
2004-02-13 11:24 ` Nikita Danilov
2004-02-16 17:56 ` Ludootje
2004-02-13 22:38 ` Randy.Dunlap [this message]
2004-02-13 8:58 ` PATCH, RFC: 2.6 Documentation/Codingstyle Giuliano Pochini
2004-02-13 9:10 ` Andrew Morton
2004-02-13 9:49 ` Michael Frank
2004-02-13 10:09 ` Nick Piggin
2004-02-13 10:50 ` Michael Frank
2004-02-18 7:39 ` Miles Bader
2004-02-13 12:44 ` viro
2004-02-13 9:19 ` David Weinehall
2004-02-13 11:42 ` Andries Brouwer
2004-02-13 12:13 ` Måns Rullgård
2004-02-13 12:42 ` Ed Tomlinson
2004-02-13 13:55 ` Giuliano Pochini
2004-02-13 14:35 ` Angelo Dell'Aera
2004-02-13 15:42 ` Giuliano Pochini
2004-02-13 15:48 ` Valdis.Kletnieks
2004-02-13 16:38 ` Angelo Dell'Aera
2004-02-13 17:03 ` Valdis.Kletnieks
2004-02-13 16:18 ` viro
2004-02-14 0:38 ` Kevin O'Connor
2004-02-14 0:56 ` Valdis.Kletnieks
2004-02-14 1:44 ` PATCH, RFC: Version 3 of 2.6 Codingstyle Michael Frank
2004-02-14 3:44 ` Dmitry Torokhov
2004-02-15 10:09 ` Jamie Lokier
2004-02-14 20:44 ` PATCH, RFC: Version 4 " Michael Frank
2004-02-14 21:27 ` viro
2004-02-16 3:47 ` PATCH, RFC: Version 5 " Michael Frank
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=20040213143821.663edcae.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.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®