From: "Chris Friesen" <cfriesen@nortel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
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 01:15:09 -0400 [thread overview]
Message-ID: <4889615D.9020706@nortel.com> (raw)
In-Reply-To: <20080724211141.4fa557ca@lxorguk.ukuu.org.uk>
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 ?
Is it reasonable for in-tree code to remain "experimental" indefinately?
Chris
next prev parent reply other threads:[~2008-07-25 5:15 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 [this message]
2008-07-25 10:05 ` Alan Cox
2008-07-25 10:41 ` Bernd Petrovitsch
2008-07-25 12:08 ` Robert P. J. Day
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=4889615D.9020706@nortel.com \
--to=cfriesen@nortel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.