LKML Archive on
help / color / mirror / Atom feed
From: "Robert P. J. Day" <>
To: Linux Kernel Mailing List <>
Subject: [PATCH] deprecated/obsolete patch
Date: Tue, 20 Feb 2007 18:20:10 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0702201818580.11849@localhost.localdomain> (raw)

  here's a slightly revised wording, if that makes it clearer:

diff --git a/init/Kconfig b/init/Kconfig
index f977086..d5ab6ec 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -29,9 +29,10 @@ config EXPERIMENTAL
 	  <file:Documentation/BUG-HUNTING>, and
 	  <file:Documentation/oops-tracing.txt> in the kernel source).

-	  This option will also make obsoleted drivers available. These are
-	  drivers that have been replaced by something else, and/or are
-	  scheduled to be removed in a future kernel release.
+	  At the moment, this option also makes obsolete drivers available,
+	  but such drivers really should be removed from the EXPERIMENTAL
+	  category and added to either DEPRECATED or OBSOLETE, depending
+	  on their status.

 	  Unless you intend to help test and develop a feature or driver that
 	  falls into this category, or you have a situation that requires
@@ -40,6 +41,29 @@ config EXPERIMENTAL
 	  you say Y here, you will be offered the choice of using features or
 	  drivers that are currently considered to be in the alpha-test phase.

+	bool "Prompt for deprecated code/drivers"
+	default y
+	---help---
+	  Code that has been tagged as "deprecated" generally still works and
+	  is probably still supported, but there is already a newer and better
+	  alternative available and you should seriously consider switching to
+	  that newer alternative.
+	  Code that is marked as deprecated for quite some time also has a
+	  tendency to eventually become "obsolete," at which point it will
+	  probably be removed entirely from the kernel.
+config OBSOLETE
+	bool "Prompt for obsolete code/drivers"
+	default n
+	---help---
+	  Code that has been tagged as "obsolete" is no longer officially
+	  supported and shouldn't play a part in any normal build.  Obsolete
+	  code might already be scheduled for removal as well, so you might
+	  want to check the file Documentation/feature-removal-schedule.txt for
+	  any proposed removal dates.
 config BROKEN

Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

             reply	other threads:[~2007-02-20 23:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-20 23:20 Robert P. J. Day [this message]
2007-02-21  1:39 ` Bartlomiej Zolnierkiewicz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0702201818580.11849@localhost.localdomain \ \ \
    --subject='Re: [PATCH] deprecated/obsolete patch' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).