From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [git pull] x86 changes for v2.6.27
Date: Mon, 14 Jul 2008 13:57:47 -0700 [thread overview]
Message-ID: <487BBDCB.7050303@zytor.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807141346170.3305@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> Things like this _really_ irritate me:
>
> Memtest (MEMTEST) [Y/n/?] (NEW) ?
>
> why the hell is that defaulting to "on"?
>
> The rule of thumb should be:
>
> NO NEW FEATURES SHOULD _EVER_ DEFAULT TO 'ON'!
>
> I do realize that developers always think that _their_ particular cool new
> feature is so important that it should default to 'on', but that's always
> the case, and it's _always_ wrong.
>
I'm a bit surprised that you'd say that for something that is a
hardware-testing feature that needs a command-line option to be enabled
at runtime. I have always presumed that the default value is the
recommended value, and I would think that that is what most people would
assume.
-hpa
next prev parent reply other threads:[~2008-07-14 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 13:50 [git pull] x86 changes for v2.6.27 Ingo Molnar
2008-07-14 20:49 ` Linus Torvalds
2008-07-14 20:57 ` H. Peter Anvin [this message]
2008-07-14 21:01 ` Linus Torvalds
2008-07-14 21:16 ` H. Peter Anvin
2008-07-14 21:25 ` Linus Torvalds
2008-07-14 22:00 ` Linus Torvalds
2008-07-15 8:35 ` Ingo Molnar
2008-07-15 2:51 ` Dave Jones
2008-07-15 4:33 ` Linus Torvalds
2008-07-16 13:54 ` Ingo Molnar
2008-07-16 13:52 ` Bartlomiej Zolnierkiewicz
2008-07-16 14:05 ` Ingo Molnar
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=487BBDCB.7050303@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 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.