From: Matthias Schniedermeyer <ms@citd.de>
To: Nicholas Wourms <nwourms@netscape.net>
Cc: Flavio Stanchina <flavio.stanchina@tin.it>, linux-kernel@vger.kernel.org
Subject: Re: Petition against kernel configuration options madness...
Date: Sun, 3 Nov 2002 23:00:23 +0100 [thread overview]
Message-ID: <20021103220023.GA16889@citd.de> (raw)
In-Reply-To: <3DC593A8.2030204@netscape.net>
On Sun, Nov 03, 2002 at 04:22:48PM -0500, Nicholas Wourms wrote:
> Flavio Stanchina wrote:
> >On Sunday 03 November 2002 21:38, Nicholas Wourms wrote:
> >
> >
> >>Stop whining, 2.5 kernels are development kernels -> not *expected* to
> >>work %100!
> >
> >
> >Correct me if I'm wrong, but we're here to work out the problems. That's
> >one of the major meanings of "development", in my experience.
> >
> >I was bitten too: I loaded my 2.4.19 configuration and looked through most
> >options, but I overlooked this keyboard/mouse thing. I think it's not
> >turned on by default if you load an existing configuration, which is
> >probably not what we want.
> >
>
> This is true, but if you are going to make a report, make a
> report, don't advocate changing something which works for
> most as it stands. From the subject, one got the idea that
> people wanted to do some willy-nilly rearranging of the
> configure options. The real issue here is that you really
> should *not* be copying 2.4 .config's over to a 2.5 tree.
> That way you'll be forced to go through all the options and
> get the proper "default" options for your platform enabled
> automatically.
So here goes the suggestion:
The config gets a version-Tag.
Changes before the second dot in the version print a warning that you
should not copy configs between major-versions. (Maybe it is better to
default to exit with the warning and an option to override the exit.)
Only configs without a version-Tag are tricky. Maybe there is a good(tm)
config-option that can be used to guess if the config is from the
current major-version (=2.5). All other configs are "old(tm)".
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
next prev parent reply other threads:[~2002-11-03 21:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 17:09 Petition against kernel configuration options madness Jos Hulzink
2002-11-03 16:05 ` Tomas Szepe
2002-11-03 18:20 ` Jos Hulzink
2002-11-03 17:52 ` Jeff Garzik
2002-11-03 19:07 ` Vojtech Pavlik
2002-11-03 19:37 ` Petr Baudis
2002-11-03 20:13 ` Vojtech Pavlik
2002-11-03 22:20 ` Petr Baudis
2002-11-03 22:32 ` [PATCH] Sane defaults for the input layer configuration Petr Baudis
2002-11-03 22:25 ` Petition against kernel configuration options madness Jos Hulzink
2002-11-04 1:40 ` Randy.Dunlap
2002-11-04 2:43 ` Miles Bader
2002-11-04 2:46 ` William Lee Irwin III
2002-11-03 20:38 ` Arador
2002-11-03 20:40 ` Nicholas Wourms
2002-11-03 21:39 ` Jos Hulzink
2002-11-03 22:04 ` Nick LeRoy
2002-11-03 21:58 ` Andries Brouwer
2002-11-03 21:59 ` Dave Jones
2002-11-03 22:18 ` Brad Hards
2002-11-04 0:06 ` Werner Almesberger
2002-11-04 13:05 ` Mr. James W. Laferriere
2002-11-03 20:38 ` Nicholas Wourms
2002-11-03 20:43 ` Arador
2002-11-03 21:11 ` Flavio Stanchina
2002-11-03 21:22 ` Nicholas Wourms
2002-11-03 21:48 ` Flavio Stanchina
2002-11-03 22:00 ` Matthias Schniedermeyer [this message]
2002-11-04 0:18 ` Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2002-11-03 20:19 Hell.Surfers
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=20021103220023.GA16889@citd.de \
--to=ms@citd.de \
--cc=flavio.stanchina@tin.it \
--cc=linux-kernel@vger.kernel.org \
--cc=nwourms@netscape.net \
/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