From: "Randy.Dunlap" <rddunlap@osdl.org>
To: David Weinehall <tao@debian.org>
Cc: theman@josephdwagner.info, ak@suse.de, rmps@joel.ist.utl.pt,
linux-kernel@vger.kernel.org
Subject: Re: RFC: Trailing blanks in source files
Date: Tue, 27 Jan 2004 11:18:24 -0800 [thread overview]
Message-ID: <20040127111824.7f76efe6.rddunlap@osdl.org> (raw)
In-Reply-To: <20040127191358.GI20879@khan.acc.umu.se>
On Tue, 27 Jan 2004 20:13:58 +0100 David Weinehall <tao@debian.org> wrote:
| On Tue, Jan 27, 2004 at 12:51:34PM -0600, Joseph D. Wagner wrote:
| > > It seems that many files [1] in the Linux source have lines with
| > > trailing blank (space and tab) characters and some even have formfeed
| > > characters. Obviously these blank characters aren't necessary.
| >
| > Actually, they are necessary.
| >
| > http://www.gnu.org/prep/standards_23.html
| > http://www.gnu.org/prep/standards_24.html
|
| Let me quote CodingStyle:
|
| "First off, I'd suggest printing out a copy of the GNU coding standards,
| and NOT read it. Burn them, it's a great symbolic gesture."
|
| That's how much relevance GNU's coding standards have to the kernel.
Thank you, I had forgotten that one and I was wondering what the
heck those web pages had to do with anything (kernel).
So please don't bother with just whitespace changes unless you
are going to cleanup a <driver | fs | module | etc> completely.
--
~Randy
kernel-janitors project: http://janitor.kernelnewbies.org/
next prev parent reply other threads:[~2004-01-27 19:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0401271544120.27260@joel.ist.utl.pt.suse.lists.linux.kernel>
2004-01-27 18:34 ` Andi Kleen
2004-01-27 18:51 ` Joseph D. Wagner
2004-01-27 19:13 ` David Weinehall
2004-01-27 19:18 ` Randy.Dunlap [this message]
2004-01-28 0:02 ` Andrew Morton
2004-01-28 3:49 ` jw schultz
2004-01-28 3:55 ` Randy.Dunlap
2004-01-28 4:53 ` Pragnesh Sampat
2004-01-27 19:31 ` Paulo Marques
2004-01-28 22:15 ` Paul Jackson
2004-01-28 22:22 ` David Weinehall
2004-01-27 19:14 ` linux
2004-01-27 15:44 Rui Saraiva
2004-01-27 16:15 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-27 16:30 ` Bas Mevissen
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=20040127111824.7f76efe6.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmps@joel.ist.utl.pt \
--cc=tao@debian.org \
--cc=theman@josephdwagner.info \
/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®