public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Henning P. Schmiedehausen" <hps@intermeta.de>
To: linux-kernel@vger.kernel.org
Subject: Removing the whitespaces??? [Was: Re: Why not "attach" patches?]
Date: Wed, 16 Jan 2002 00:11:35 +0000 (UTC)	[thread overview]
Message-ID: <a22gfn$c15$1@forge.intermeta.de> (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>

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.

apply patches. Run this. Rinse. Repeat. :-)

--- cut ---

mkdir /usr/src/linux.noblanks

(
  cd /usr/src/linux
  find . -type d -exec mkdir -p /usr/src/linux.noblanks/{} \;
  for i in `find . -type f`; do
    perl -ne 's/[        ]+$//; print;' < ${i} > /usr/src/linux.noblanks/${i}
  done
)

diff -ur /usr/src/linux /usr/src/linux.noblanks | mail -s "blanks removed" torvalds@transmeta.com 

rm -rf /usr/src/linux.noblanks
--- cut ---

(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.

	Regards
		Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen       -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH     hps@intermeta.de

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   info@intermeta.de
D-91054 Buckenhof     Fax.: 09131 / 50654-20   

  reply	other threads:[~2002-01-16  0:11 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             ` Henning P. Schmiedehausen [this message]
2002-01-16  4:16               ` Removing the whitespaces??? [Was: Re: Why not "attach" patches?] Andreas Dilger
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='a22gfn$c15$1@forge.intermeta.de' \
    --to=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