From: David Weinehall <tao@acc.umu.se>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "Michael S. Tsirkin" <mst@mellanox.co.il>, linux-kernel@vger.kernel.org
Subject: Re: kernel guide to space (updated)
Date: Fri, 29 Jul 2005 19:57:14 +0200 [thread overview]
Message-ID: <20050729175714.GE9841@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.LNX.4.61.0507290929250.26861@yvahk01.tjqt.qr>
On Fri, Jul 29, 2005 at 09:40:14AM +0200, Jan Engelhardt wrote:
[snip]
> Would it be reasonable to say that the first column can be a space?
> Some editors (e.g. joe) list the function in some status bar and do
> that based on the fact that all C code in a function is indented, and
> only the function header is non-indented. Putting a label statement
> fools the algorithm. joe-bug or option for freedom?
I'd definitely call that a joe-bug. Adding extra space for no good
reason is just silly; for consistency we'd have to add a space for the
case <foo>: labels also...
Regards: David
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2005-07-29 17:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 14:53 Michael S. Tsirkin
2005-07-28 15:52 ` linux-os (Dick Johnson)
2005-07-28 16:45 ` John W. Linville
2005-07-28 16:40 ` Dmitry Torokhov
2005-07-29 7:29 ` Jan Engelhardt
2005-07-29 7:40 ` Jan Engelhardt
2005-07-29 10:13 ` Joost Remijn
2005-07-29 17:57 ` David Weinehall [this message]
2005-07-29 19:52 ` Jan Engelhardt
2005-07-29 20:13 ` David Weinehall
2005-07-30 11:41 ` Jan Engelhardt
2005-07-30 13:38 ` David Weinehall
2005-07-30 18:32 ` Jan Engelhardt
2005-07-30 9:58 ` Vincent Hanquez
2005-08-01 2:15 ` Miles Bader
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=20050729175714.GE9841@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@mellanox.co.il \
/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®