From: Sam Ravnborg <sam@ravnborg.org>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kconfig update
Date: Mon, 10 Mar 2003 20:12:45 +0100 [thread overview]
Message-ID: <20030310191244.GA1715@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0303101046590.5042-100000@serv>
On Mon, Mar 10, 2003 at 11:00:02AM +0100, Roman Zippel wrote:
> verbose mode. If you skip the oldconfig step, the config tool is called
> anyway and checks the configuration and only asks as necessary. The same
> mode could be used for oldconfig, but I didn't want to change the
> behaviour needlessly.
The reason to respond is that all the output from conf looks useless.
What is the usage of conf being so verbose?
If it is required then keep it. But making conf that verbose only
because configure was that verbose . There is no point in that.
Not a needlessly change, but more in the area - it was about time..
Sam
next prev parent reply other threads:[~2003-03-10 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-09 3:57 [PATCH] kconfig update Roman Zippel
2003-03-09 8:59 ` Christoph Hellwig
2003-03-09 12:14 ` Petr Baudis
2003-03-09 12:46 ` Roman Zippel
2003-03-09 19:01 ` Sam Ravnborg
2003-03-09 19:30 ` Roman Zippel
2003-03-09 19:34 ` Sam Ravnborg
2003-03-09 20:18 ` Roman Zippel
2003-03-09 21:15 ` Sam Ravnborg
2003-03-10 10:00 ` Roman Zippel
2003-03-10 19:12 ` Sam Ravnborg [this message]
[not found] ` <20030314144329.GA2768@wanadoo.fr>
[not found] ` <Pine.LNX.4.44.0303141602330.5042-100000@serv>
2003-03-14 19:36 ` [PATCH] kconfig update, GTK+ updated Romain Lievin
-- strict thread matches above, loose matches on Subject: below --
2003-05-28 22:59 [PATCH] kconfig update Roman Zippel
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=20030310191244.GA1715@mars.ravnborg.org \
--to=sam@ravnborg.org \
--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