On Mon, 14 Jul 2008, Ingo Molnar 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. 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 --
| Linus Torvalds | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Mike Galbraith | Re: regression: CD burning (k3b) went broke |
| Con Kolivas | Re: -mm merge plans for 2.6.23 |
git: | |
| Gerrit Renker | [PATCH 24/37] dccp: Processing Confirm options |
| Linus Torvalds | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Woodhouse | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
