From: David Woodhouse <dwmw2@infradead.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: What about make mergeconfig ?
Date: Wed, 25 Oct 2006 07:59:59 +0100 [thread overview]
Message-ID: <1161759599.27622.54.camel@shinybook.infradead.org> (raw)
In-Reply-To: <1161755164.22582.60.camel@localhost.localdomain>
On Wed, 2006-10-25 at 15:46 +1000, Benjamin Herrenschmidt wrote:
>
> make mergeconfig <path_to_file>
>
> That would merge all entries in the specified file with the
> current .config. By mergeing, that basically means that rule:
>
> N + N = N
> m + N = m
> Y + N = Y
> m + Y = Y
We have something vaguely similar in the Fedora package (I think it's
only in the CVS tree rather than in the SRPM itself, but the CVS tree is
public too).
http://cvs.fedora.redhat.com/viewcvs/*checkout*/rpms/kernel/devel/merge.pl?rev=1.9
It doesn't do quite what you asked for -- it works with 'incremental'
configuration. So any options specified in _any_ form in the second
config are overridden in the output. It lets us start with a generic
config, then apply options (turning stuff both on and off) for PowerPC
in general, and then for specific builds on top of that.
--
dwmw2
next prev parent reply other threads:[~2006-10-25 6:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 5:46 What about make mergeconfig ? Benjamin Herrenschmidt
2006-10-25 6:59 ` David Woodhouse [this message]
2006-10-25 10:01 ` Jesper Juhl
2006-10-25 13:52 ` Benjamin Herrenschmidt
2006-10-25 10:18 ` Dick Streefland
2006-10-25 11:39 ` Jan Engelhardt
2006-10-25 12:07 ` Dick Streefland
2006-10-26 8:00 ` Jan Engelhardt
2006-10-26 9:03 ` Geert Uytterhoeven
2006-10-26 11:25 ` Jan Engelhardt
2006-10-26 12:00 ` Geert Uytterhoeven
2006-10-27 9:58 ` Jan Engelhardt
2006-10-27 11:14 ` Geert Uytterhoeven
2006-10-25 17:41 ` Christoph Lameter
2006-10-26 10:50 ` Samuel Tardieu
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=1161759599.27622.54.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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