From: David Weinehall <david@southpole.se>
To: Paul Jackson <pj@sgi.com>
Cc: Paulo Marques <pmarques@grupopie.com>,
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: Wed, 28 Jan 2004 23:22:09 +0100 [thread overview]
Message-ID: <20040128222209.GE16675@khan.acc.umu.se> (raw)
In-Reply-To: <20040128141540.05cf8bbb.pj@sgi.com>
On Wed, Jan 28, 2004 at 02:15:40PM -0800, Paul Jackson wrote:
> Joseph D. Wagner
> > Actually, they are necessary.
>
> Paulo Marques
> > where is the part that requires *trailing* spaces?
>
> No where. Joseph was ambiguous - I'd guess he meant:
> Actually, formfeeds are necessary.
Which is of course not the case either...
Regards: David Weinehall
--
/) David Weinehall <tao@acc.umu.se> /) Northern lights wander (\
// Maintainer of the v2.0 kernel // Dance across the winter sky //
\) http://www.acc.umu.se/~tao/ (/ Full colour fire (/
next prev parent reply other threads:[~2004-01-28 22:22 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 ` RFC: Trailing blanks in source files 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 [this message]
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=20040128222209.GE16675@khan.acc.umu.se \
--to=david@southpole.se \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=pmarques@grupopie.com \
--cc=rmps@joel.ist.utl.pt \
--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