From: Stuart Young <sgy@amc.com.au>
To: linux-kernel@vger.kernel.org
Cc: hps@intermeta.de
Subject: Re: Removing the whitespaces??? [Was: Re: Why not "attach" patches?]
Date: Wed, 16 Jan 2002 11:26:18 +1100 [thread overview]
Message-ID: <5.1.0.14.0.20020116111518.023f2c00@mail.amc.localnet> (raw)
In-Reply-To: <a22gfn$c15$1@forge.intermeta.de>
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>
At 12:11 AM 16/01/02 +0000, Henning P. Schmiedehausen wrote:
>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.
This 'sort' of thing would be a good idea for 2.5 IMHO (pref. asap), mainly
to get it out of the way! It would probably be a good idea to do this on a
tree just before it matures too (eg: when 2.5 migrates to 2.6/3.0/whatever).
The savings to other trees are probably not worth the effort involved for
what we gain back (at the moment anyway).
You'll probably find that there are other things about that might save a
few bytes here and there too (and at the same time might clean the code up
a bit and make it more readable).
Stuart Young - sgy@amc.com.au
(aka Cefiar) - cefiar1@optushome.com.au
[All opinions expressed in the above message are my]
[own and not necessarily the views of my employer..]
next prev parent reply other threads:[~2002-01-16 0:26 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 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
2002-01-17 8:56 ` Ravindra Jaju
2002-01-16 0:26 ` Stuart Young [this message]
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 18:50 ` Richard Gooch
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=5.1.0.14.0.20020116111518.023f2c00@mail.amc.localnet \
--to=sgy@amc.com.au \
--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
all inboxes | Powered by JetHome®