From: Tilman Schmidt <tilman@imap.cc>
To: Satyam Sharma <satyam.sharma@gmail.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
LKML <linux-kernel@vger.kernel.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>
Subject: Re: Linux 2.6.22-rc1
Date: Tue, 15 May 2007 12:43:47 +0200 [thread overview]
Message-ID: <46498EE3.8010907@imap.cc> (raw)
In-Reply-To: <a781481a0705141934u6b369dd5ob1715f14890af914@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2205 bytes --]
Hi,
Satyam Sharma schrieb:
>> * Since Jens Axboe's stance ["default y idiocy"] is to have
>> these menus disabled by default, people should most likely
>> enable them first before they will be able to enter them.
>
> I do agree that anything non-essential (even if it's just a presentation
> menu that doesn't affect builds) must be default n.
It's tricky for "make oldconfig" when introducing a new "menuconfig"
around some previously existing "config"s, because just accepting
the default for the new option then causes previously selected
ones to be silently dropped. But I don't know a perfect solution
for that. Perhaps we'll just have to live with it. Or perhaps a
warning message along the line of "deselecting option xxx" would
be in order.
> IMHO, the real problem with "default y" menuconfig's, is that they
> cause unpleasant surprises to those folks that use the text-based
> "make oldconfig". They get confronted with choices that they never
> bothered about (or even knew existed) previously, and have no
> idea how to answer them -- same problem faced by Tilman, when
> he used oldconfig.
It's actually the other way around, all those options now tucked
underneath the menuconfig were previously directly visible, so
selecting "y" (either explicitly or by default) makes everything
work as before while "n" very conveniently skips them all.
It's really quite nice if you know how it works. The only thing
that's missing is instructions for those seeing it for the first
time.
> IMHO, those using "oldconfig" are often looking towards doing
> things quickly ... doesn't help them if they have default y menu's
> that they need to "?" upon then to see what they're really about.
Well, yes and no. I am of course trying to get through the new
options as quickly as possible. But if I hit an option I don't
understand then typing "?" is the quickest way to sort it out,
so it's doubly annoying if that yields nothing.
Thanks,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-05-15 10:44 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 3:20 Linux 2.6.22-rc1 Linus Torvalds
2007-05-13 9:20 ` Jan Engelhardt
2007-05-17 6:55 ` Len Brown
2007-05-13 9:29 ` Linux 2.6.22-rc1, 'nother randconfig Jan Engelhardt
2007-05-14 11:44 ` David Howells
2007-05-14 17:23 ` Jan Engelhardt
2007-05-15 9:26 ` David Howells
2007-05-15 9:40 ` Jan Engelhardt
2007-05-13 9:47 ` [PATCH] driver core: fix warning of temporarily unused multithreaded probing function (was: Re: Linux 2.6.22-rc1) Borislav Petkov
2007-05-14 8:06 ` Cornelia Huck
2007-05-13 12:44 ` Linux 2.6.22-rc1 Alessandro Suardi
2007-05-13 12:44 ` Indan Zupancic
2007-05-13 17:10 ` Antonino Ingargiola
2007-05-13 17:53 ` Linus Torvalds
2007-05-13 18:50 ` Antonino Ingargiola
2007-05-14 6:10 ` Jean Delvare
2007-05-14 8:34 ` Antonino Ingargiola
2007-05-14 12:14 ` Jean Delvare
2007-05-14 13:28 ` Antonino Ingargiola
2007-05-14 15:21 ` Jean Delvare
2007-05-14 16:04 ` Antonino Ingargiola
2007-05-14 16:23 ` Michal Piotrowski
2007-05-14 18:08 ` Jean Delvare
2007-05-14 18:25 ` Antonino Ingargiola
2007-05-14 16:30 ` Linus Torvalds
2007-05-14 18:24 ` Jean Delvare
2007-05-14 18:43 ` Linus Torvalds
2007-05-14 19:28 ` Jean Delvare
2007-05-14 19:53 ` Jeff Garzik
2007-05-14 20:18 ` Christoph Hellwig
2007-05-14 20:17 ` Christoph Hellwig
2007-05-14 20:15 ` Christoph Hellwig
2007-05-15 20:31 ` CONFIG_BREAK_MY_MACHINE was " Pavel Machek
2007-05-16 18:11 ` CONFIG_BREAK_MY_MACHINE Jean Delvare
2007-05-17 8:32 ` CONFIG_BREAK_MY_MACHINE Hans de Goede
2007-05-17 8:47 ` CONFIG_BREAK_MY_MACHINE Pavel Machek
2007-05-13 18:19 ` Linux 2.6.22-rc1 Tilman Schmidt
2007-05-13 23:20 ` David Miller
2007-05-13 23:32 ` Roland Dreier
2007-05-13 23:57 ` Tilman Schmidt
2007-05-14 4:37 ` Sam Ravnborg
2007-05-14 4:53 ` David Miller
2007-05-14 6:21 ` Satyam Sharma
2007-05-14 17:21 ` Jan Engelhardt
2007-05-14 17:32 ` Stefan Richter
2007-05-14 20:27 ` Jan Engelhardt
2007-05-14 18:01 ` Tilman Schmidt
2007-05-14 20:33 ` Jan Engelhardt
2007-05-14 21:40 ` Tilman Schmidt
2007-05-14 22:09 ` Stefan Richter
2007-05-15 3:02 ` Satyam Sharma
2007-05-15 8:08 ` Jan Engelhardt
2007-05-14 21:54 ` Stefan Richter
2007-05-15 2:34 ` Satyam Sharma
2007-05-15 2:42 ` Satyam Sharma
2007-05-15 6:05 ` Stefan Richter
2007-05-15 6:01 ` Stefan Richter
2007-05-15 8:16 ` Jan Engelhardt
2007-05-16 1:52 ` Satyam Sharma
2007-05-16 6:29 ` Stefan Richter
2007-05-16 9:56 ` Satyam Sharma
2007-05-15 10:43 ` Tilman Schmidt [this message]
2007-05-16 1:39 ` Satyam Sharma
2007-05-16 9:14 ` Tilman Schmidt
2007-05-16 9:17 ` Satyam Sharma
2007-05-15 5:35 ` Michael Gerdau
2007-05-13 20:51 ` 2.6.22-rc1: loop.c Alexey Dobriyan
2007-05-14 3:52 ` Jeremy Fitzhardinge
2007-05-13 22:53 ` Linux 2.6.22-rc1 Jeff Chua
2007-05-14 1:08 ` andrew hendry
2007-05-14 7:49 ` V4L Regression (Was: Linux 2.6.22-rc1) Robert Fitzsimons
2007-05-15 4:14 ` Linux 2.6.22-rc1 andrew hendry
2007-05-15 4:38 ` Linus Torvalds
2007-05-15 5:10 ` andrew hendry
2007-05-15 15:57 ` Linus Torvalds
2007-05-15 22:50 ` andrew hendry
-- strict thread matches above, loose matches on Subject: below --
2007-05-13 6:00 Jeff Chua
2007-05-13 6:13 ` Jeff Chua
2007-05-13 8:04 ` Jan Engelhardt
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=46498EE3.8010907@imap.cc \
--to=tilman@imap.cc \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=satyam.sharma@gmail.com \
--cc=stefanr@s5r6.in-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.