[src/trunk]: src/external/mit/lua/dist README.import with step-by-step import...

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

details:   https://anonhg.NetBSD.org/src/rev/20cd02feed58
branches:  trunk
changeset: 834265:20cd02feed58
user:      alnsn <alnsn%NetBSD.org@localhost>
date:      Sat Aug 04 17:47:26 2018 +0000

description:
README.import with step-by-step import instruction.

diffstat:

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

diffs (24 lines):

diff -r 95e3af5e40e0 -r 20cd02feed58 external/mit/lua/dist/README.import
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/external/mit/lua/dist/README.import       Sat Aug 04 17:47:26 2018 +0000
@@ -0,0 +1,20 @@
+How to import Lua x.y.z
+=======================
+
+1. Untar a new version to a directory called dist.work or even
+   somethere outside of the tree.
+2. Run lua2netbsd script inside that directory.
+3. Run 'cvs import src/external/mit/lua/dist LUA LUA_<<x_y_z>>'.
+   It's very important to run it from inside the right direcory!
+4. Move the dist directory away (is it optional?).
+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.
+8. Commit your changes.
+
+Vendor branches are usually named LUA_<<x_y_z>> but if there was a problem
+with cvs import, they can be named differently.
+
+The last imported vendor branch is called LUA_5_3_5_try2.