Added CR for readability

into mysql.com:/usr/local/home/marty/MySQL/mysql-4.1

into mysql.com:/home/dlenev/src/mysql-4.1-bg11060

INSERT ... SELECT with UNION" (reviewed version).

Altough bug manifest itself only starting from 5.0 it is better to
apply fix to 4.1 to keep some assumptions true and make code more
future-proof.

  Use the Perl version of mysql-test-run

  Corrected path to 'mysql_fix_privilege_tables'

into mysql.com:/usr/local/home/marty/MySQL/mysql-4.1

  Corrected path to 'mysql_fix_privilege_tables'
  Corrected dummy --manager-port to take integer argument

into mysql.com:/usr/local/home/marty/MySQL/mysql-4.1

into dl145c.mysql.com:/home/ndbdev/tomas/mysql-4.1

  remove typecheck in ndb handler not needed

  Added dummy --manager-port flag, for backward compatibility
  Back port from 5.0, correction of paths to SSL pem files
mtr_cases.pl:
  Removed hard coded exclude list for embedded server
mysql-test-run.pl:
  Set environment variable MYSQL_SHOW, to be used in test cases

into mysql.com:/Users/kent/mysql/bk/mysql-4.1

into serg.mylan:/usr/home/serg/Abk/mysql-4.1

  fixed 64bit bug in lenght store/retrive in cache

Bug#8367 "low log doesn't gives complete information about prepared 
statements"
Implement status variables for prepared statements commands (a port of
the patch by Andrey Hristov).
See details in comments to the changed files.
No test case as there is no way to test slow log/general log in 
mysqltest.

ALTER, OPTIMIZE and ANALYZE statements".
In 4.1 we disabled logging of slow admin statements. The fix adds an 
option to enable it back.
No test case (slow log is not tested in the test suite), but tested
manually.
+ post-review fixes (word police mainly).

Removed SHOW BINLOG EVENTS in test case for ps-protocol and row-based replication

into serg.mylan:/usr/home/serg/Abk/mysql-4.1

into mysql.com:/home/stewart/Documents/MySQL/4.1/bug11132

portability alignment issues.

into mysql.com:/Users/kent/mysql/bk/mysql-4.1

In 4.1 (it is different in 5.0), we do not use the mgm connection after fetching the
configuration (and if we did, we would have to have calls to check the connection and
reconnect if needed - in case the mgm server had restarted) so we can disconnect after
first use.

This means we won't have connections stuck in CLOSE_WAIT when the mgm server shuts down.

into mysql.com:/usr/local/home/marty/MySQL/mysql-4.1

into mysql.com:/Users/kent/mysql/bk/mysql-4.1

into mysql.com:/export/space/pekka/ndb/version/my41

into dl145c.mysql.com:/home/ndbdev/tomas/mysql-4.1

into dl145c.mysql.com:/home/ndbdev/tomas/mysql-4.1

  Correction for test case of bug #11142.

  Added a test case for bug #11142.
item_cmpfunc.cc:
  Fixed bug #11142.
  Implementation of Item_func_nullif::is_null was corrected.

  Logging to logging@openlogging.org accepted
DbtcMain.cpp, testTimeout.cpp:
  Bug  #11290 TransactionInactiveTimeout = 0 does not result in infinite timeout

into igor-inspiron.creware.com:/home/igor/dev/mysql-4.1-0

  Added a test case for bug #11167.
sql_select.cc:
  Fixed bug #11167.
  In 4.1 char/varchar fields are limited by 255 characters in
  length that make them longer than 255 bytes in size for such
  character sets as UTF8. The functions store_record_in_cache
  and read_cached_records did not take into account this
  Moreover the code did not take into account that the size
  of the varchar fields in 5.0 can be up to 65535 bytes