From: Bas Mevissen <ml@basmevissen.nl>
To: unlisted-recipients:; (no To-header on input)
Cc: rmps@joel.ist.utl.pt, linux-kernel@vger.kernel.org,
yoshfuji@linux-ipv6.org
Subject: Re: RFC: Trailing blanks in source files
Date: Tue, 27 Jan 2004 17:30:46 +0100 [thread overview]
Message-ID: <40169236.2050606@basmevissen.nl> (raw)
In-Reply-To: <20040128.011537.81631272.yoshfuji@linux-ipv6.org>
YOSHIFUJI Hideaki / ???? wrote:
> In article <Pine.LNX.4.58.0401271544120.27260@joel.ist.utl.pt> (at Tue, 27 Jan 2004 15:44:56 +0000 (WET)), Rui Saraiva <rmps@joel.ist.utl.pt> says:
>
>
>> 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.
>
>
> I do not like to change this if it is done blindly.
>
Agree. But if you compile a allconfigyes kernel before and after and
they appear to be binary equal, we know we are pretty safe :-)
Regards,
Bas.
next prev parent reply other threads:[~2004-01-27 16:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 15:44 RFC: Trailing blanks in source files Rui Saraiva
2004-01-27 16:15 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-27 16:30 ` Bas Mevissen [this message]
[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
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
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=40169236.2050606@basmevissen.nl \
--to=ml@basmevissen.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rmps@joel.ist.utl.pt \
--cc=yoshfuji@linux-ipv6.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