From: Rob Landley <rob@landley.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] make miniconfig (take 2)
Date: Fri, 25 Nov 2005 16:20:12 -0600 [thread overview]
Message-ID: <200511251620.12996.rob@landley.net> (raw)
In-Reply-To: <20051125220934.GA2268@elf.ucw.cz>
On Friday 25 November 2005 16:09, Pavel Machek wrote:
> Ouch, I guess I killed my .config :-(. It seems that interrupted
> miniconfig.sh leaves .config in close to empty state...
That's why it insists you rename it in order to run it.
I intend to fix that somewhat in a newer version of the sucker by having the
script intercept signals and restore .config on the way out, but it can't be
fully reliable (not against kill -9) because kconfig overwrites .config and
the script is repeatedly running allnoconfig. (I can probably bypass the
makefile and feed it some strange command line argument, but what Kconfig to
run it on gets us into architecture dependence issues the make file handles
for us...)
> I'm not sure what I did wrong last time, it worked this time. My
> miniconfig is 6K instead of 46K, good. Still its quite long. Thanks!
You mentioned you set a lot of options. :)
I agree scripts/miniconfig.sh is clumsy. I'm thinking about improvements
(both to how it works and to the user interface), but I need to catch up on
some other stuff first...
> Pavel
Rob
--
Steve Ballmer: Innovation! Inigo Montoya: You keep using that word.
I do not think it means what you think it means.
next prev parent reply other threads:[~2005-11-25 22:20 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 12:29 Quick and dirty miniconfig howto, with feature suggestions Rob Landley
2005-11-20 3:08 ` Roman Zippel
2005-11-20 5:54 ` Rob Landley
2005-11-21 6:15 ` [PATCH] make miniconfig Rob Landley
2005-11-21 16:06 ` [PATCH] make miniconfig (take 2) Rob Landley
2005-11-21 17:26 ` Pavel Machek
2005-11-21 17:46 ` Rob Landley
2005-11-21 17:36 ` Pavel Machek
2005-11-21 17:50 ` Rob Landley
2005-11-21 18:28 ` Pavel Machek
2005-11-21 18:53 ` Rob Landley
2005-11-21 19:24 ` Pavel Machek
2005-11-22 5:14 ` Rob Landley
2005-11-22 22:54 ` Pavel Machek
2005-11-23 8:58 ` Rob Landley
2005-11-23 13:21 ` Pavel Machek
2005-11-24 3:19 ` Rob Landley
2005-11-25 19:45 ` Pavel Machek
2005-11-25 21:45 ` Rob Landley
2005-11-25 22:09 ` Pavel Machek
2005-11-25 22:20 ` Rob Landley [this message]
2005-11-26 2:34 ` Kyle Moffett
2005-11-26 12:25 ` Rob Landley
2005-11-26 14:19 ` Pavel Machek
2005-11-26 15:51 ` Rob Landley
2005-11-24 4:02 ` Rob Landley
2005-11-25 19:46 ` Pavel Machek
2005-11-26 1:53 ` Andre Noll
2005-11-22 5:17 ` Rob Landley
2005-11-24 13:56 ` Roman Zippel
2005-11-24 17:45 ` Rob Landley
2005-11-25 1:48 ` Roman Zippel
2005-11-25 8:18 ` Rob Landley
2005-11-25 15:02 ` Roman Zippel
2005-11-25 16:47 ` Rob Landley
2005-11-25 21:12 ` Rob Landley
2005-11-27 23:20 ` Roman Zippel
2005-11-28 0:59 ` Rob Landley
2005-11-29 1:00 ` Roman Zippel
2005-11-29 2:26 ` Rob Landley
2005-11-30 2:29 ` Roman Zippel
2005-11-20 3:25 ` Quick and dirty miniconfig howto, with feature suggestions Rob Landley
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=200511251620.12996.rob@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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.