From: Jeff Garzik <jeff@garzik.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: maturity and status and attributes, oh my!
Date: Sat, 01 Sep 2007 06:43:30 -0400 [thread overview]
Message-ID: <46D94252.3000505@garzik.org> (raw)
In-Reply-To: <46D92D8E.9020508@s5r6.in-berlin.de>
Stefan Richter wrote:
> But I can state requirements for the 'experimental' marker, from the POV
> of a volunteer driver support guy:
> - Show it in big letters in the Kconfig prompt of an experimental
> feature.
> - Explain at appropriate place(s) what the particular caveats of the
> feature are.
> That's it. I am not aware of a need to evaluate this marker in routines
> which calculate the .config, unlike the 'broken' marker.
Correct.
> BTW, the requirements of communication in feature removal processes are
> similar to a degree. But feature removal involves more active two-way
> communication and is tied to a schedule.
'deprecated' and 'obsolete' are very different beasts from the other
statuses. They are largely just a marker of opinion of the developer,
and are largely treated as synonyms.
Code that was never marked deprecated nor obsolete often appears in
Documentation/feature-removal-schedule.txt, and eventually gets removed.
Feature deprecation and removal is a very amorphous concept that does
not fit well at all into Kconfig markers, unlike experimental/broken.
Jeff
next prev parent reply other threads:[~2007-09-01 10:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 21:38 maturity and status and attributes, oh my! Robert P. J. Day
2007-08-31 22:02 ` Jeff Garzik
2007-09-01 6:35 ` Jan Engelhardt
2007-09-01 9:06 ` Robert P. J. Day
2007-08-31 22:36 ` Stefan Richter
2007-09-01 1:23 ` Robert P. J. Day
2007-09-01 9:14 ` Stefan Richter
2007-09-01 9:21 ` Robert P. J. Day
2007-09-01 9:47 ` Stefan Richter
2007-09-01 9:54 ` Robert P. J. Day
2007-09-01 13:14 ` Jan Engelhardt
2007-09-01 13:53 ` Jeff Garzik
2007-09-01 10:43 ` Jeff Garzik [this message]
2007-09-01 10:52 ` Robert P. J. Day
2007-09-01 11:06 ` Jeff Garzik
2007-09-01 13:44 ` Bartlomiej Zolnierkiewicz
2007-09-01 13:52 ` Jeff Garzik
2007-09-01 14:27 ` Stefan Richter
[not found] ` <Pine.LNX.4.64.0709010435070.26137@localhost.localdomain>
2007-09-01 9:27 ` Stefan Richter
2007-09-01 9:41 ` Robert P. J. Day
2007-09-01 17:22 ` Dave Jones
2007-09-01 17:58 ` Robert P. J. Day
2007-09-01 18:06 ` Robert P. J. Day
2007-09-01 18:24 ` Dave Jones
2007-08-31 23:02 ` Dave Jones
2007-09-01 8:34 ` Robert P. J. Day
-- strict thread matches above, loose matches on Subject: below --
2007-08-31 23:29 Mitchell Erblich
2007-09-01 1:33 ` Robert P. J. Day
2007-09-01 6:39 ` Jan Engelhardt
2007-09-01 7:02 ` Robert P. J. Day
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=46D94252.3000505@garzik.org \
--to=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=stefanr@s5r6.in-berlin.de \
/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