public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <wa@almesberger.net>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Nicholas Wourms <nwourms@netscape.net>,
	Flavio Stanchina <flavio.stanchina@tin.it>,
	linux-kernel@vger.kernel.org
Subject: Re: Petition against kernel configuration options madness...
Date: Sun, 3 Nov 2002 21:18:15 -0300	[thread overview]
Message-ID: <20021103211815.L2599@almesberger.net> (raw)
In-Reply-To: <20021103220023.GA16889@citd.de>; from ms@citd.de on Sun, Nov 03, 2002 at 11:00:23PM +0100

Matthias Schniedermeyer wrote:
> The config gets a version-Tag.

This would only be helpful if you also had a description of what the
user is expected to change. (And once you have this, you might as
well automate the process a little more, as I've just described in
another posting.)

Just telling the user that there might be problems isn't very helpful,
in particular since most such version conflicts would be false alarms,
e.g. name changes of some obscure controller I don't have anyway. I
think most people are aware of the fact that "make oldconfig" may
produce nonsense, but it's still annoying if it does.

Another easy extension to consider: after "make oldconfig", print
the options that were found in .config, but which don't exist anymore.
I've actually proposed this already two years ago, see also
http://marc.theaimsgroup.com/?l=linux-kernel&m=97298980521513&w=2

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

  reply	other threads:[~2002-11-04  0:12 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
2002-11-04  0:18         ` Werner Almesberger [this message]
  -- 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=20021103211815.L2599@almesberger.net \
    --to=wa@almesberger.net \
    --cc=flavio.stanchina@tin.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ms@citd.de \
    --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