From: Krzysztof Halasa <khc@pm.waw.pl>
To: "John Stoffel" <john@stoffel.org>
Cc: Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] intel-rng: Undo mess made by an 80 column extremist
Date: Sat, 09 Jun 2007 22:41:11 +0200 [thread overview]
Message-ID: <m3bqfosvx4.fsf@maximus.localdomain> (raw)
In-Reply-To: <18024.46902.682920.924521@stoffel.org> (John Stoffel's message of "Thu, 7 Jun 2007 21:56:06 -0400")
"John Stoffel" <john@stoffel.org> writes:
> Thinking about it more, I wonder if Krysztof is bitching more about
> the tab width of 8 characters? I know that it ticks me off,
> indenting by two spaces is plenty for me to follow the flow, along
> with Emacs and braces closure indication.
Well, 8 might be too long but I wouldn't be able to read the code
with 2-chars tabs. Even on a large wall display.
4 chars, maybe, but I'm not sure. 8 chars is great except that the
lines are too short.
Obviously it's the space taken by indentation, the "real" line
length of ~ 70 chars (such as in this msg) is ok.
--
Krzysztof Halasa
prev parent reply other threads:[~2007-06-09 20:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 15:22 [PATCH] intel-rng: Undo mess made by an 80 column extremist Alan Cox
2007-06-07 15:23 ` Jeff Garzik
2007-06-07 15:44 ` Alan Cox
2007-06-07 17:22 ` Jeff Garzik
2007-06-07 21:17 ` Krzysztof Halasa
2007-06-07 21:32 ` Alistair John Strachan
2007-06-07 22:06 ` Krzysztof Halasa
2007-06-08 1:08 ` H. Peter Anvin
2007-06-08 1:25 ` Jeff Garzik
2007-06-08 10:11 ` Peter Zijlstra
2007-06-09 20:33 ` Krzysztof Halasa
2007-06-07 22:32 ` Daniel Hazelton
2007-06-07 22:37 ` Krzysztof Halasa
2007-06-07 23:01 ` Daniel Hazelton
2007-06-07 22:46 ` Jesper Juhl
2007-06-07 23:04 ` Daniel Hazelton
2007-06-08 1:44 ` John Stoffel
2007-06-08 1:47 ` Jeff Garzik
2007-06-08 1:56 ` John Stoffel
2007-06-08 2:07 ` Jeff Garzik
2007-06-08 2:11 ` John Stoffel
2007-06-08 18:21 ` Ingo Oeser
2007-06-09 20:41 ` Krzysztof Halasa [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=m3bqfosvx4.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=john@stoffel.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 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.