From: James Simmons <jsimmons@infradead.org>
To: Samuel Flory <sflory@rackable.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Christoph Hellwig <hch@infradead.org>,
Roman Zippel <zippel@linux-m68k.org>, michaelm <admin@www0.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: Make menuconfig broken
Date: Tue, 22 Jul 2003 21:30:17 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0307222129070.17797-100000@phoenix.infradead.org> (raw)
In-Reply-To: <3F1D91F0.2020900@rackable.com>
> Well there are 2 issues here:
>
> 1) How to handle "make oldconfig" on 2.4 config files. Which may not be
> fixable in a manner that doesn't involve really ugly code.
>
> 2) That make menuconfig|xconfig on a clean 2.6 tree results in a kernel
> that doesn't have console support. This will be something that will
> come up over and over again in the future, and does not require ugly
> hacks to fix.
Instead of hacking up a oldconfig why not have the system detect old
config files and refuse to build it and tell the user to start from
scratch. I think this is acceptable.
next prev parent reply other threads:[~2003-07-22 20:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 16:35 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc michaelm
2003-07-21 16:49 ` James Simmons
2003-07-21 17:02 ` Charles Lepple
2003-07-22 0:37 ` Samuel Flory
2003-07-22 0:42 ` Make menuconfig broken Samuel Flory
2003-07-22 7:19 ` Sam Ravnborg
2003-07-22 9:50 ` Roman Zippel
2003-07-22 13:24 ` Vojtech Pavlik
2003-07-22 16:47 ` James Simmons
2003-07-22 18:17 ` Christoph Hellwig
2003-07-22 19:16 ` Sam Ravnborg
2003-07-22 19:35 ` Samuel Flory
2003-07-22 19:46 ` Charles Lepple
2003-07-22 20:30 ` James Simmons [this message]
2003-07-23 22:53 ` bill davidsen
2003-07-23 22:48 ` bill davidsen
2003-07-22 18:00 ` Samuel Flory
2003-07-22 19:21 ` michaelm
2003-07-22 2:49 ` 2.6.0-test1 won't go further than "uncompressing" on a p1/32MB pc Thomas Molina
2008-02-02 17:29 make menuconfig broken Michal Zachar
2008-02-02 19:50 ` 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=Pine.LNX.4.44.0307222129070.17797-100000@phoenix.infradead.org \
--to=jsimmons@infradead.org \
--cc=admin@www0.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sflory@rackable.com \
--cc=vojtech@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).