From: Andreas Dilger <adilger@turbolabs.com>
To: "Henning P. Schmiedehausen" <hps@intermeta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Removing the whitespaces??? [Was: Re: Why not "attach" patches?]
Date: Tue, 15 Jan 2002 21:16:35 -0700 [thread overview]
Message-ID: <20020115211635.T11251@lynx.adilger.int> (raw)
In-Reply-To: <Pine.LNX.4.33.0201151448050.5892-100000@xanadu.home> <Pine.LNX.4.33.0201151405250.9053-100000@segfault.osdlab.org> <20020115151629.N11251@lynx.adilger.int> <a22gfn$c15$1@forge.intermeta.de>
In-Reply-To: <a22gfn$c15$1@forge.intermeta.de>; from hps@intermeta.de on Wed, Jan 16, 2002 at 12:11:35AM +0000
On Jan 16, 2002 00:11 +0000, Henning P. Schmiedehausen wrote:
> Andreas Dilger <adilger@turbolabs.com> writes:
> >Well, it would be a feature if it knew enough to only remove whitespace
> >at the end of "+" lines in context diffs. Then we wouldn't have 200kB
> >of useless whitespace in the kernel sources.
>
> (This is a TAB and a space in the square brackets above.
> Don't use \s. Trust me.)
>
> linux-2.2.20.tar.bz2: 15,751,285 bytes
> linux-2.2.20-nbl.tar.bz2: 15,608,085 bytes
>
> Patch Size (uncompressed): 17,815,166 bytes (yes this _is_ 17,4 MBytes)
> (compressed, bzip2): 3,322,456 bytes
>
> One mega-patch to shear off about 140 KBytes from the compressed (and
> about 170 k from the unpacked (94488 vs. 94316 KBytes ) kernel source
> would (while it may be the biggest single "reduce-size-of-kernel-tree
> patch" in years :-) ) a little gross.
Oh, I'm not advocating sending in a huge patch _just_ to remove the
useless whitespace (which includes trailing spaces/tabs and [space][tab]
combinations), but it would be nice if someone is setting up a patchbot
to remove such whitespace in new or modified lines in a patch.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-01-16 16:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 17:44 Why not "attach" patches? Martin Eriksson
2002-01-15 17:47 ` David S. Miller
2002-01-15 17:52 ` Martin Dalecki
2002-01-15 18:04 ` Linus Torvalds
2002-01-15 18:50 ` Richard Gooch
2002-01-15 19:28 ` Alan Cox
2002-01-15 19:29 ` Davide Libenzi
2002-01-15 19:49 ` Nicolas Pitre
2002-01-15 22:09 ` Patrick Mochel
2002-01-15 22:16 ` Andreas Dilger
2002-01-16 0:11 ` Removing the whitespaces??? [Was: Re: Why not "attach" patches?] Henning P. Schmiedehausen
2002-01-16 4:16 ` Andreas Dilger [this message]
2002-01-17 8:56 ` Ravindra Jaju
2002-01-16 0:26 ` Stuart Young
2002-01-15 23:13 ` Why not "attach" patches? Urban Widmark
2002-01-15 23:51 ` Sebastian Benoit
2002-01-15 19:59 ` Jeff Garzik
2002-01-21 16:15 ` Daniel Phillips
2002-01-22 18:17 ` H. Peter Anvin
2002-01-24 6:59 ` Kai Henningsen
2002-01-16 11:46 ` Christoph Rohland
2002-01-16 17:22 ` Linus Torvalds
2002-01-15 17:57 ` Kent Borg
2002-01-15 19:38 ` Martin Eriksson
2002-01-15 19:48 ` Anton Altaparmakov
2002-01-15 23:34 ` Johan Kullstam
2002-01-15 18:02 ` Linus Torvalds
2002-01-15 18:39 ` Andi Kleen
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=20020115211635.T11251@lynx.adilger.int \
--to=adilger@turbolabs.com \
--cc=hps@intermeta.de \
--cc=linux-kernel@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