bk commit into 4.1 tree (petr:1.2307)

[Petr Chardin]

Below is the list of changes that have just been committed into a local
4.1 repository of pchardin. When pchardin does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet
  1.2307 05/06/22 01:39:52 petr@stripped +1 -0
  fix README file to be more verbose match actual situation (recomitted to push into 4.1)

  mysql-test/README
    1.9 05/06/22 01:39:49 petr@stripped +11 -2
    fix README file to be more verbose match actual situation

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	petr
# Host:	production.mysql.com
# Root:	/usersnfs/pchardin/mysql-4.1

--- 1.8/mysql-test/README	2005-03-23 17:45:41 +01:00
+++ 1.9/mysql-test/README	2005-06-22 01:39:49 +02:00
@@ -2,8 +2,17 @@
 the currently existing test cases, simply execute ./mysql-test-run in
 this directory. It will fire up the newly built mysqld and test it.
 
-If you want to run the test with a running MySQL server use the --external
-option to mysql-test-run.
+If you want to run a test with a running MySQL server use the --extern
+option to mysql-test-run. Please note that in this mode the test suite
+expects user to specify test names to run. Otherwise it falls back to the
+normal "non-extern" behaviour. The reason is that some tests
+could not run with external server. Here is the sample command
+to test "alias" and "analyze" tests on external server:
+
+mysql-test-run --extern alias analyze
+
+To match your setup you might also need to provide --socket, --user and
+other relevant options.
 
 Note that you do not have to have to do make install, and you could
 actually have a co-existing MySQL installation - the tests will not