[PATCH] add feature-removal-schedule.txt documentation

From: Greg KH
Date: Thu Jan 06 2005 - 19:19:50 EST


On Thu, Jan 06, 2005 at 03:26:21PM -0800, Andrew Morton wrote:
> Which begs the question "how do we ever get rid of these things when we
> have no projected date for Linux-2.8"?
>
> I'd propose:
>
> a) Create Documentation/feature-removal-schedule.txt which describes
> things which are going away, when, why, who is involved, etc.

Ok, I'll bite, here's a patch that does just that. Look good?

thanks,

greg k-h

-----------

Add Documentation/feature-removal-schedule.txt as a way to notify
everyone when and what is going to be removed.

Signed-off-by: Greg Kroah-Hartman <greg@xxxxxxxxx>

diff -Nru a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
--- /dev/null Wed Dec 31 16:00:00 196900
+++ b/Documentation/feature-removal-schedule.txt 2005-01-06 15:54:40 -08:00
@@ -0,0 +1,17 @@
+The following is a list of files and features that are going to be
+removed in the kernel source tree. Every entry should contain what
+exactly is going away, why it is happening, and who is going to be doing
+the work. When the feature is removed from the kernel, it should also
+be removed from this file.
+
+---------------------------
+
+What: devfs
+When: July 2005
+Files: fs/devfs/*, include/linux/devfs_fs*.h and assorted devfs
+ function calls throughout the kernel tree
+Why: It has been unmaintained for a number of years, has unfixable
+ races, contains a naming policy within the kernel that is
+ against the LSB, and can be replaced by using udev.
+Who: Greg Kroah-Hartman <greg@xxxxxxxxx>
+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/