From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] cleanup swiotlb.c a bit
Date: Thu, 06 Jan 2005 20:00:11 +0000 [thread overview]
Message-ID: <16861.39115.110083.6350@napali.hpl.hp.com> (raw)
In-Reply-To: <200501060945.12364.jbarnes@engr.sgi.com>
>>>>> On Thu, 6 Jan 2005 11:50:56 -0800, Jesse Barnes <jbarnes@engr.sgi.com> said:
>> It's not opinion, it's reality. Unless someone goes through all
>> the files in the top-level directories and formats them to 80
>> cols, this won't change.
Jesse> I'd be happy to do that if you're ok with it.
Eh, I'm talking about linux/kernel/* etc, so it's really Andrew and
Linus who'd have to be OK with it.
If you can fix those, I'd be happy to adjust the ia64 files to fit
within 80 cols.
Jesse> The long lines have always irritated me a little. I think I
Jesse> understand why you like them though--with long lines you can
Jesse> fit slightly more code on the screen vertically, which can be
Jesse> a help, but I don't think they're common enough for that to
Jesse> be very compelling...
I don't particularly like 100 cols. I'd be happy if all (major) Linux
kernel files fit into 80 cols, it's just that in reality, you need 100
cols to look at most important kernel files.
--david
next prev parent reply other threads:[~2005-01-06 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 17:45 [PATCH] cleanup swiotlb.c a bit Jesse Barnes
2005-01-06 19:38 ` David Mosberger
2005-01-06 19:42 ` Jesse Barnes
2005-01-06 19:47 ` Matthew Wilcox
2005-01-06 19:48 ` David Mosberger
2005-01-06 19:50 ` Jesse Barnes
2005-01-06 20:00 ` David Mosberger [this message]
2005-01-06 20:00 ` David Mosberger
2005-01-06 20:01 ` Matthew Wilcox
2005-01-06 20:06 ` Andi Kleen
2005-01-06 20:07 ` Jesse Barnes
2005-01-06 20:10 ` Matthew Wilcox
2005-01-06 20:11 ` Luck, Tony
2005-01-06 21:19 ` David Mosberger
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=16861.39115.110083.6350@napali.hpl.hp.com \
--to=davidm@napali.hpl.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