From: Eric Anopolsky <erpo41@gmail.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: sct@redhat.com, akpm@linux-foundation.org, adilger@clusterfs.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.24 patch] let EXT4DEV_FS depend on BROKEN
Date: Wed, 02 Jan 2008 13:51:32 -0800 [thread overview]
Message-ID: <1199310692.5786.53.camel@dione> (raw)
In-Reply-To: <20080102195146.GB15898@does.not.exist>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
> > Isn't CONFIG_EXPERIMENTAL enough?
>
> Most people and all distributions use CONFIG_EXPERIMENTAL=y simply
> because too many options (including options required for hardware
> support) depend on it.
Maybe I'm wrong, but I think most people use the distro-provided
precompiled kernels. This is only a danger to people who insist on
compiling their own kernels but who don't know enough to investigate
things labeled "EXPERIMENTAL" before typing Y.
IMHO, these people are a dying breed since modern distros seem to do a
good job at preventing problems that drive ordinary users to compile
their own kernels in the first place. IMHO, it's reasonable to expect
the small minority of Linux users who want to compile their own kernels
to learn that "EXPERIMENTAL" means something.
Cheers,
Eric
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-01-02 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 1:32 [2.6.24 patch] let EXT4DEV_FS depend on BROKEN Adrian Bunk
2008-01-02 17:41 ` Andreas Dilger
2008-01-02 19:51 ` Adrian Bunk
2008-01-02 21:51 ` Eric Anopolsky [this message]
2008-01-04 5:41 ` Valdis.Kletnieks
2008-01-02 22:43 ` Eric Sandeen
2008-01-02 20:40 ` Alan Cox
2008-01-02 18:26 ` Diego Calleja
2008-01-02 21:16 ` Adrian Bunk
2008-01-02 21:21 ` Alan Cox
2008-01-02 21:31 ` Trond Myklebust
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=1199310692.5786.53.camel@dione \
--to=erpo41@gmail.com \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/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