From: Sam Ravnborg <sam@ravnborg.org>
To: devzero@web.de
Cc: linux-kbuild@vger.kernel.org
Subject: Re: defconfigs size reduction?
Date: Wed, 6 Feb 2008 22:13:55 +0100 [thread overview]
Message-ID: <20080206211355.GC12043@uranus.ravnborg.org> (raw)
In-Reply-To: <142056111@web.de>
On Sun, Feb 03, 2008 at 01:29:00PM +0100, devzero@web.de wrote:
> hi there,
>
> i found that there are a lot of deconfigs bundled with every kernel-release. (about 335 on my suse box)
>
> summed up, that`s 6,3M and 311 KLOC (Kilo Lines of Configuration :)
>
> i think, that`s quite a lot.
>
> if i strip the comments ( real comments and "# CONFIGOPT is not set") and the blank lines from that, the size reduces to 1.9M and 86 KLOC.
>
The primary issue with defconfigs are that they get
outdated rather quickly. They are often several kernel releases
behind.
This is a much more relvant issue to address than a few wasted MB of
cheap disk space.
So anything that just make it a tad more difficult to update
a defconfig will not be accepted if the only aim is to save
disk space.
Sam
prev parent reply other threads:[~2008-02-06 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 12:29 defconfigs size reduction? devzero
2008-02-06 21:13 ` Sam Ravnborg [this message]
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=20080206211355.GC12043@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=devzero@web.de \
--cc=linux-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.