From: Andres Salomon <dilinger@queued.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: kbuild-devel@lists.sourceforge.net, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: UNS: Re: [PATCH] kconfig: add *_silentdefconfig feature for config targets
Date: Mon, 22 Oct 2007 15:00:15 -0400 [thread overview]
Message-ID: <20071022150015.72d9ebef@ephemeral> (raw)
In-Reply-To: <Pine.LNX.4.64.0708211809110.1817@scrub.home>
On Tue, 21 Aug 2007 18:21:55 +0200 (CEST)
Roman Zippel <zippel@linux-m68k.org> wrote:
> Hi,
>
> On Tue, 21 Aug 2007, Andres Salomon wrote:
>
> > > I would really like to avoid another input mode.
> > > I think it be better to implement this as a combination of "-s -D
> > > <default>" and the silent mode is adjusted to read another config
> > > instead of .config if defconfig_file is set.
> > >
> >
> > As would I; however, that requires using getopt() (or equivalent).
> > I wasn't sure if there was some opposition to this..
>
> I'm not sure how getopt() would change much (besides changing the
> "if" to a "while"), but I don't really mind either way.
>
It would allow more flexibilty; being able to specify multiple
arguments, for example. Unfortunately, I haven't had much time to work
on this, but I did do the getopt patch. Since it's been sitting on my
drive for a while, I should probably send it out before I lose it. :)
next prev parent reply other threads:[~2007-10-22 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 0:40 [PATCH] kconfig: add *_silentdefconfig feature for config targets Andres Salomon
2007-08-21 15:29 ` Roman Zippel
2007-08-21 15:41 ` UNS: " Andres Salomon
2007-08-21 16:21 ` Roman Zippel
2007-10-22 19:00 ` Andres Salomon [this message]
2007-08-22 8:07 ` [kbuild-devel] " Sam Ravnborg
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=20071022150015.72d9ebef@ephemeral \
--to=dilinger@queued.net \
--cc=akpm@linux-foundation.org \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox