[src/pgoyette-compat]: src/doc Remove "alias" entry from the To-Do list - it'...

[pgoyette <pgoyette%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/dff34e4b7ca0
branches:  pgoyette-compat
changeset: 321015:dff34e4b7ca0
user:      pgoyette <pgoyette%NetBSD.org@localhost>
date:      Mon Mar 12 02:03:20 2018 +0000

description:
Remove "alias" entry from the To-Do list - it's already in the Done pile.

diffstat:

 doc/COMPAT-branch-notes |  9 ---------
 1 files changed, 0 insertions(+), 9 deletions(-)

diffs (19 lines):

diff -r a6c533ab08ad -r dff34e4b7ca0 doc/COMPAT-branch-notes
--- a/doc/COMPAT-branch-notes   Mon Mar 12 01:59:31 2018 +0000
+++ b/doc/COMPAT-branch-notes   Mon Mar 12 02:03:20 2018 +0000
@@ -36,15 +36,6 @@
 
    (There are several instances of this in the net routing table code.)
 
-2. Implement a mechanism for modules to include "aliases".  This would
-   allow a single module file to contain multiple module table entries
-   (for example, a single file for the compat module could include
-   compat_80, compat_70, compat_60, ...).  Then, other modules could
-   depend on individual names.  For example, module compat_xyz could
-   depend on compat_70, and the dependency would be met by either the
-   "everything" compat module (with all of its aliases) or by a 7.0-
-   specific module.
-
 2. Using the alias mechanism, split compat (and perhaps compat_sysv)
    into multiple version-specific modules.  Note that in addition to
    updating the module code, this would also require changes to