From: David Weinehall <tao@acc.umu.se>
To: Padraig Brady <padraig@antefacto.com>
Cc: Mark Hahn <hahn@physics.mcmaster.ca>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] remove trailing whitespace
Date: Fri, 23 Nov 2001 21:45:00 +0100 [thread overview]
Message-ID: <20011123214500.A5770@khan.acc.umu.se> (raw)
In-Reply-To: <Pine.LNX.4.10.10111231440260.1920-100000@coffee.psychology.mcmaster.ca> <3BFEB2DC.6040208@antefacto.com>
In-Reply-To: <3BFEB2DC.6040208@antefacto.com>; from padraig@antefacto.com on Fri, Nov 23, 2001 at 08:34:36PM +0000
On Fri, Nov 23, 2001 at 08:34:36PM +0000, Padraig Brady wrote:
> I used sed, but yes the following does
> the same as downloading and applying the patch:
> find linux -type f | xargs perl -wi -pe 's/[<space><tab>]+$//'
> (obviously replace <space> & <tab> with the appropriate chars).
>
> Note also that after (bz2) compression the space saving drops
> from 224,654 to 139,669 bytes, which is still good.
>
> Padraig.
Running Lindent on the kerneltree would be far more yielding, as
it would, apart from removing extraoneous whitespace, also format
all code in a sane manner. However, this is unlikely to ever happen; I
seem to recall that Linus has commented on this before.
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:[~2001-11-23 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10111231440260.1920-100000@coffee.psychology.mcmaster.ca>
2001-11-23 20:34 ` Padraig Brady
2001-11-23 20:45 ` David Weinehall [this message]
2001-11-23 17:20 Padraig Brady
2001-11-25 16:00 ` vda
2001-11-25 12:25 ` Russell King
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=20011123214500.A5770@khan.acc.umu.se \
--to=tao@acc.umu.se \
--cc=hahn@physics.mcmaster.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=padraig@antefacto.com \
--cc=torvalds@transmeta.com \
/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®