[Gc-linux-cvs] CVSROOT modules,1.2,1.3

[<aot...@us...>]

Update of /cvsroot/gc-linux/CVSROOT
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv18300

Modified Files:
	modules 
Log Message:
Define status of modules, so cvs co -s outputs something more useful.

Index: modules
===================================================================
RCS file: /cvsroot/gc-linux/CVSROOT/modules,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- modules	15 Aug 2005 04:12:47 -0000	1.2
+++ modules	15 Aug 2005 17:25:18 -0000	1.3
@@ -25,9 +25,25 @@
 # can be useful for creating a module that consists of many directories
 # spread out over the entire source repository.
 
-binutils	binutils/
-htdocs		htdocs/
-ipl		ipl/
-libgx		libgx/
-libsdl		libsdl/
-linux		linux/
+# Module status may be arbitrary. Thusly, the project-specific format is:
+#	modulename [-s status,address] directory
+#
+# Where "status" may be any one of:
+#	maintained	Module is currently maintained.
+#	unmaintained	Module is no longer maintained.
+#	obsolete	Module is now obsolete.
+#
+# And "address" is the sourceforge.net address of whoever is currently
+# primarily associated with the module.
+#
+# "unmaintained" and "obsolete" strictly need not be accompanied by an
+# address, but this is still recommended for historical reasons, ie. to
+# indicate who was last associated with the module. Otherwise, they may
+# be accompanied by the name of the superseding module.
+
+binutils	-s maintained,aot...@us...		binutils/
+htdocs		-s maintained,he...@us...		htdocs/
+ipl		-s unmaintained,rob...@us...	ipl/
+libgx		-s maintained,pal...@us...		libgx/
+libsdl		-s maintained,he...@us...		libsdl/
+linux		-s maintained,aot...@us...		linux/