[src/trunk]: src/external/mit/lua/dist Don't use $NetBSD$ in a sentence, refe...

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

details:   https://anonhg.NetBSD.org/src/rev/fb92a8a190fe
branches:  trunk
changeset: 834266:fb92a8a190fe
user:      alnsn <alnsn%NetBSD.org@localhost>
date:      Sat Aug 04 17:53:29 2018 +0000

description:
Don't use $NetBSD$ in a sentence, refer to them as 'RCS identifiers'.

diffstat:

 external/mit/lua/dist/README.import |  4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diffs (14 lines):

diff -r 20cd02feed58 -r fb92a8a190fe external/mit/lua/dist/README.import
--- a/external/mit/lua/dist/README.import       Sat Aug 04 17:47:26 2018 +0000
+++ b/external/mit/lua/dist/README.import       Sat Aug 04 17:53:29 2018 +0000
@@ -10,8 +10,8 @@
 5. Run 'cvs up -dP' to bring the new import to the tree.
 6. Run 'cvs up -j LUA_<<previous_version>> -j LUA_<<x_y_z>>'.
    It will generate many conflicts.
-7. Resolve conflicts. Most (if not all) conflicts are around $NetBSD: README.import,v 1.1 2018/08/04 17:47:26 alnsn Exp $
-   RCS identifiers.
+7. Resolve conflicts. Most (if not all) conflicts are around RCS
+   identifiers.
 8. Commit your changes.
 
 Vendor branches are usually named LUA_<<x_y_z>> but if there was a problem