From: Adrian Bunk <bunk@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove CONFIG_EXPERIMENTAL
Date: Tue, 1 Jan 2008 18:33:38 +0200 [thread overview]
Message-ID: <20080101163337.GX2360@does.not.exist> (raw)
In-Reply-To: <20080101160708.5bb5cc2a@the-village.bc.nu>
On Tue, Jan 01, 2008 at 04:07:08PM +0000, Alan Cox wrote:
> On Tue, 1 Jan 2008 17:17:51 +0200
> Adrian Bunk <bunk@kernel.org> wrote:
>
> > On Tue, Jan 01, 2008 at 02:23:44PM +0000, Alan Cox wrote:
> > > On Tue, 1 Jan 2008 15:48:09 +0200
> > > Adrian Bunk <bunk@kernel.org> wrote:
> > >
> > > > This patch removes the EXPERIMENTAL option and all dependencies on
> > > > EXPERIMENTAL since they are pointless.
> > >
> > > NAK
> > >
> > > Experimental is an important guide to driver and code quality.
> > >...
> >
> > History has shown that EXPERIMENTAL tags in many areas of the kernel
> > have not been maintained in a way that they would be usable as a guide.
>
> Repeatedly posting crud does not make it right. As far as I can see the
> tags are pretty honest for the most part - some have been experimental
> for ten years but the 3c507 driver *has* always been a beta grade driver.
So smbfs is still considered rock solid while no serious distribution
would be crazy enough to ship the EXPERIMENTAL NFSv4 support to their
customers?
I'm not claiming that all EXPERIMENTAL tags were wrong [1], but many
were wrong.
Plus the fact that CONFIG_EXPERIMENTAL controlled so many different
things with one switch that CONFIG_EXPERIMENTAL=n .config's are really
rare.
> > And as soon as you need _one_ driver or feature depending on
> >> That's not about consensus,
>
> It should be.
You removed the context.
The fact that Andrew has not applied a three times sent patch does not
necessarily imply there was any problem with a patch - "no answer" on
linux-kernel always translates to "continue patchbombing".
> Alan
cu
Adrian
[1] after all, even with a random distribution many of them
were right ;-)
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-01-01 16:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-01 13:48 [2.6 patch] remove CONFIG_EXPERIMENTAL Adrian Bunk
2008-01-01 14:23 ` Alan Cox
2008-01-01 15:17 ` Adrian Bunk
2008-01-01 16:07 ` Alan Cox
2008-01-01 16:33 ` Adrian Bunk [this message]
2008-01-01 17:35 ` Alan Cox
2008-01-01 18:14 ` Jon Smirl
2008-01-02 0:06 ` Adrian Bunk
2008-01-01 14:26 ` Ingo Molnar
2008-01-01 14:30 ` Alan Cox
2008-01-01 14:57 ` Adrian Bunk
2008-01-01 15:06 ` Ingo Molnar
2008-01-01 18:04 ` Jan Engelhardt
2008-01-10 22:18 ` Ralf Baechle
2008-01-11 10:41 ` Paul Mundt
-- strict thread matches above, loose matches on Subject: below --
2007-12-11 22:21 Adrian Bunk
2007-11-25 16:16 Adrian Bunk
2007-11-26 12:27 ` Pavel Machek
2007-11-26 18:57 ` Adrian Bunk
2007-11-27 3:44 ` Valdis.Kletnieks
2007-11-27 4:34 ` Dave Jones
2007-11-27 6:13 ` Valdis.Kletnieks
2007-11-28 12:38 ` Krzysztof Halasa
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=20080101163337.GX2360@does.not.exist \
--to=bunk@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox