From: Brent Casavant <bcasavan@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Code style (was Re: [PATCH] SN2 user-MMIO CPU migration)
Date: Fri, 27 Jan 2006 16:08:51 +0000 [thread overview]
Message-ID: <20060127100149.K64411@chenjesu.americas.sgi.com> (raw)
On Fri, 27 Jan 2006, Prarit Bhargava wrote:
> I understand your concern, however, Documentation/CodingStyle is explicit
> about this -- do not exceed 80 columns.
I view it like cooking: following a recipe to the letter may produce
consistent and generally good results, but when you run out of butter
you may have to make do with margarine.
Brent
--
Brent Casavant All music is folk music. I ain't
bcasavan@sgi.com never heard a horse sing a song.
Silicon Graphics, Inc. -- Louis Armstrong
reply other threads:[~2006-01-27 16:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060127100149.K64411@chenjesu.americas.sgi.com \
--to=bcasavan@sgi.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