From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Grant Coady <gcoady.lk@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: how much stuff is no longer "EXPERIMENTAL"?
Date: Fri, 25 Jul 2008 08:08:50 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0807250806370.3366@localhost.localdomain> (raw)
In-Reply-To: <20080724211141.4fa557ca@lxorguk.ukuu.org.uk>
On Thu, 24 Jul 2008, Alan Cox wrote:
> > legitimately experimental content in the source tree. surely
> > *some* of that is suitably mature such that that dependency can be
> > dropped.
>
> What is the connection between age of code and experimental status ?
perhaps nothing, perhaps lots. *of course* there can be features
that are both long-lived and still experimental. just as, of course,
there is stuff that was (properly) tagged as EXPERIMENTAL ages ago
that has long since stabilized and can afford to stop being
experimental.
just a small nagging for folks to take a quick look at what no
longer needs to be tagged that way, that's all.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
next prev parent reply other threads:[~2008-07-25 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 15:14 how much stuff is no longer "EXPERIMENTAL"? Robert P. J. Day
2008-07-24 18:29 ` Grant Coady
2008-07-24 20:06 ` Robert P. J. Day
2008-07-24 20:09 ` Roland Dreier
2008-07-24 20:10 ` Robert P. J. Day
2008-07-24 20:11 ` Alan Cox
2008-07-25 5:15 ` Chris Friesen
2008-07-25 10:05 ` Alan Cox
2008-07-25 10:41 ` Bernd Petrovitsch
2008-07-25 12:08 ` Robert P. J. Day [this message]
2008-07-25 12:51 ` Stefan Richter
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.0807250806370.3366@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gcoady.lk@gmail.com \
--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