From: Al Stone <ahs3@fc.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] reformat ivt.S for 80-column use
Date: Thu, 10 Aug 2006 14:51:46 +0000 [thread overview]
Message-ID: <1155221506.12634.85.camel@deimos> (raw)
In-Reply-To: <1155168978.12634.62.camel@deimos>
On Thu, 2006-08-10 at 08:52 -0400, Jes Sorensen wrote:
> >>>>> "David" = David Mosberger-Tang <David.Mosberger@acm.org> writes:
>
> David> On 10 Aug 2006 03:24:02 -0400, Jes Sorensen <jes@sgi.com>
> David> wrote:
> >> Some of the really complex code is unnecessarily hard to follow due
> >> to this, so I give you my ack!
>
> David> Huh? Ever heard of the window resize button? 100 cols will be
> David> just fine. IA-64 assembly code is one area where it really
> David> helps to have more than 80 cols. Just my 2 cents, of course...
>
> It's all a matter of personal preference of course, but I don't like
> resizing my windows depending on what files I am reading. Given that
> CodingStyle calls for 80 columns I prefer to keep my windows at 80
> columns (just as I try to stick to the glibc style when I write glibc
> code, as much as I dislike it).
It is indeed a personal preference; for myself, I don't really care
that much whether it's 80 or 100 (or 132, to _really_ date myself).
The only reasons I had for the patch were (1) personal difficulty with
100-column windows on a laptop (some of us older folks need slightly
larger fonts :), and (2) the recommendations in CodingStyle (independent
of whether I agree with them or not).
--
Ciao,
al
----------------------------------------------------------------------
Al Stone Alter Ego:
Open Source and Linux R&D Debian Developer
Hewlett-Packard Company http://www.debian.org
E-mail: ahs3@fc.hp.com ahs3@debian.org
----------------------------------------------------------------------
prev parent reply other threads:[~2006-08-10 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 0:16 [PATCH] reformat ivt.S for 80-column use Al Stone
2006-08-10 7:24 ` Jes Sorensen
2006-08-10 12:48 ` David Mosberger-Tang
2006-08-10 12:52 ` Jes Sorensen
2006-08-10 14:51 ` Al Stone [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=1155221506.12634.85.camel@deimos \
--to=ahs3@fc.hp.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox