From: Sam Ravnborg <sam@ravnborg.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Paul Mackerras <paulus@samba.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
davej@redhat.com
Subject: Re: Linux 2.6.25-rc8
Date: Thu, 3 Apr 2008 20:18:30 +0200 [thread overview]
Message-ID: <20080403181830.GA32397@uranus.ravnborg.org> (raw)
In-Reply-To: <1207227337.3224.6.camel@vader.jdub.homelinux.org>
>
> > Those defconfigs would be much smaller and change much less often if
> > they could be expressed as a delta from some other defconfig. So we'd
> > end up with a small number of base defconfigs plus a set of board
> > defconfigs that would say effectively "use the options from that other
> > defconfig, plus turn this on and that off".
>
> IIRC, Fedora builds their kernels using such a mechanism, though it's
> done in the RPM specfile with a perl script. Maybe that's something to
> look at to start with.
kconfig allready allow you to override values simply by appending to
the end of the .config file.
So it is a matter of creating the proper stuff around to:
1) use it
2) make is simple to update defconfigs
A simple extract delta between two config
I'm not up to do that at the moment - but it is doable.
And I would hate to see the defconfig disappear just because
they are so visible in Linus' dirstat.
Sam
next prev parent reply other threads:[~2008-04-03 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 20:08 Linus Torvalds
2008-04-01 21:42 ` Paul Mackerras
2008-04-02 14:50 ` Linus Torvalds
2008-04-02 18:54 ` Adrian Bunk
2008-04-03 4:08 ` Paul Mackerras
2008-04-03 12:55 ` Josh Boyer
2008-04-03 18:18 ` Sam Ravnborg [this message]
2008-04-02 0:23 ` Stephen Rothwell
2008-04-02 3:03 ` Linus Torvalds
2008-04-02 3:09 ` Linus Torvalds
2008-04-02 18:57 ` Adrian Bunk
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=20080403181830.GA32397@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davej@redhat.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=torvalds@linux-foundation.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®