From: Roman Zippel <zippel@linux-m68k.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Erlend Aasland <erlend-a@ux.his.no>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.5][RFC] Make mconf inform user about supported make targets
Date: Wed, 5 Mar 2003 02:21:12 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0303050219250.1336-100000@serv> (raw)
In-Reply-To: <20030304191311.GB1917@mars.ravnborg.org>
Hi,
On Tue, 4 Mar 2003, Sam Ravnborg wrote:
> > Solution: Get mconf to tell the user about arch-specific targets,
> > instead of i386 targets.
>
> I see no need for this patch.
> Most architectures today (if not all) has a sensible default target.
>
> So changing mconf to print something like:
> "Next, you may run 'make' to build your kernel."
>
> Should be a good enough guide for the user.
I agree and actually I'd like to remove that message completely from the
config tools. It's the job of kbuild to tell the user what to do next.
bye, Roman
prev parent reply other threads:[~2003-03-05 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 11:30 [PATCH 2.5][RFC] Make mconf inform user about supported make targets Erlend Aasland
2003-03-04 19:13 ` Sam Ravnborg
2003-03-05 1:21 ` Roman Zippel [this message]
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.44.0303050219250.1336-100000@serv \
--to=zippel@linux-m68k.org \
--cc=erlend-a@ux.his.no \
--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;
as well as URLs for NNTP newsgroup(s).