README: Update testing section.

README.md

@@ -107,16 +107,24 @@ warning/error and other options for controling compilation.
 Testing
 -------
 
+Test results should always be included with a pull request that modifies
+functionality. There is a simple process for doing this, described here:
+
 `Test` is an active test directory that contains test input and a
 subdirectory `baseResults` that contains the expected results of the
 tests.  Both the tests and `baseResults` are under source-code control.
 Executing the script `./runtests` will generate current results in
 the `localResults` directory and `diff` them against the `baseResults`.
-When you want to update the tracked test results, they need to be
-copied from `localResults` to `baseResults`.
 
-There are some tests borrowed from LunarGLASS.  If LunarGLASS is
-missing, those tests just won't run.
+When you want to update the tracked test results, they need to be
+copied from `localResults` to `baseResults`.  This can be done by
+the `bump` shell script.
+
+The list of files tested comes from `testlist`, and lists input shaders
+in this directory, which must all be public for this to work.  However,
+you can add your own private list of tests, not tracked here, by using
+`localtestlist` to list non-tracked tests.  This is automatically read
+by `runtests` and included in the `diff` and `bump` process.
 
 Basic Internal Operation
 ------------------------

glslang/Include/revision.h

@@ -2,5 +2,5 @@
 // For the version, it uses the latest git tag followed by the number of commits.
 // For the date, it uses the current date (when then script is run).
 
-#define GLSLANG_REVISION "3.0.741"
+#define GLSLANG_REVISION "3.0.743"
 #define GLSLANG_DATE "09-Sep-2015"