From: terry white <twhite@aniota.com>
To: linux-config@vger.kernel.org
Subject: Re: merge two kernel .config 's into one union of the two
Date: Thu, 29 Jun 2006 12:54:47 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0606291240490.4485@yossarian.aniota.com> (raw)
In-Reply-To: <BAY108-F33277CA7526555E113070AA37C0@phx.gbl>
... ciao:
: on "6-29-2006" "John Lumby" writ:
: but also (of course) a valid .config
i'm not sure that a trivial task.
: suggest any method at all for achieving this?
i use the following to find differences in .config files. it assumes
those copied to "config-[0-9]*". typically, '[0-9]*' a two digit minor
version number. you might want to tweak to taste.
#!/bin/sh
#
# find difference between ./.config files for linux
echo
echo Configuration differences found in \"config.diff\"
fgrep -v \# config-[0-9]* | sort -t ":" -k 2,2 \
| uniq -s 10 -u | sort > config.diff
--
... i'm a man, but i can change,
if i have to , i guess ...
next prev parent reply other threads:[~2006-06-29 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1751243AbWF2STT/20060629181919Z+5@vger.kernel.org>
2006-06-29 18:30 ` merge two kernel .config 's into one union of the two John Lumby
2006-06-29 19:54 ` terry white [this message]
2006-07-01 16:32 ` John Lumby
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=Pine.LNX.4.58.0606291240490.4485@yossarian.aniota.com \
--to=twhite@aniota.com \
--cc=linux-config@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).