From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [git pull] x86 changes for v2.6.27
Date: Mon, 14 Jul 2008 13:49:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0807141346170.3305@woody.linux-foundation.org> (raw)
In-Reply-To: <20080714135034.GA7013@elte.hu>
On Mon, 14 Jul 2008, Ingo Molnar wrote:
>
> Please pull the latest x86 git tree from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86/for-linus
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.
The only really acceptable reason to add a new config feature and make it
default to 'y' is that it's actually an old feature that just didn't have
a config option, so not defaulting to it will actually break peoples
existing configurations.
If some distro wants to enable features by default for their users, that's
their issue. But we should not do it for them.
Linus
next prev parent reply other threads:[~2008-07-14 20:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 13:50 Ingo Molnar
2008-07-14 20:49 ` Linus Torvalds [this message]
2008-07-14 20:57 ` H. Peter Anvin
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=alpine.LFD.1.10.0807141346170.3305@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome