public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Matt LaPlante <kernel1@cyberdogtech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A little coding style nugget of joy
Date: 19 Sep 2007 19:13:54 +0200	[thread overview]
Message-ID: <p73odfyvar1.fsf@bingen.suse.de> (raw)
In-Reply-To: <20070919123401.9369534d.kernel1@cyberdogtech.com>

Matt LaPlante <kernel1@cyberdogtech.com> writes:

> Since everyone loves random statistics, here are a few gems to give you a break from your busy day:
> 
> Number of lines in the 2.6.22 Linux kernel source that include one or more trailing whitespaces: 135209
> Bytes saved by removing said whitespace: 151809

You don't actually save anything on disk on most file systems
(essentially everything except reiserfs on current Linux)
because all files are rounded to block size (normally 4K) 

Same in page cache.

And in tar files bzip2/gzip is very good at compacting them.

> Lines in the (unified) diff: 455437
> Size of the diff: 15M
> People brave enough to submit the patch: ~0

Many kernel maintainers automatically remove trailing white space on any new 
lines these days. So as the kernel keeps changing it should eventually all
disappear; except on essentially dead code.

-Andi

  reply	other threads:[~2007-09-19 17:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 16:34 A little coding style nugget of joy Matt LaPlante
2007-09-19 17:13 ` Andi Kleen [this message]
2007-09-19 21:22   ` Andy Lutomirski
2007-09-19 21:30     ` Andi Kleen
2007-09-19 21:39       ` Andrew Lutomirski
2007-09-20  9:20 ` Pádraig Brady
2007-09-20 10:11   ` Robert P. J. Day
2007-09-20 14:04     ` Scott Preece

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=p73odfyvar1.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=kernel1@cyberdogtech.com \
    --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