into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b6551

into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-4.1

  Reorder options, revise --hex-blob help string.

  Remove duplicated innodb max purge lag code

into pcgem.rdg.cyberkinetica.com:/usr/home/acurtis/work/bug6469

into pcgem.rdg.cyberkinetica.com:/usr/home/acurtis/work/bug6469

  better printouts in ndb_test_platform

  fixed so that connectring option works

  made sleep time for second master larger so that it has time to start

    removed some errorcodes not used

  fixed typo

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1

into mysql.com:/home/mysql_src/mysql-4.1-clean

my_umask and my_umask_dir initialization has been moved to the my_init() func.

  Handle some additional Texinfo tags that were being missed.

into mysql.com:/home/mysql_src/mysql-4.1-clean

no new message in 4.1 (causes merge issues with 5.0). Using ER_UNKNOW_ERROR and hardcoded message string instead.

into mysql.com:/home/my/mysql-4.1

(Needed to check if memory allocated with mysql_once_init() has been freed)

into mysql.com:/users/kboortz/daily/work/mysql-4.1-wax

WL#1596 "make mysqldump --master-data --single-transaction able to do online dump of InnoDB AND report reliable
binlog coordinates corresponding to the dump".
The good news is that now mysqldump can be used to get an online backup of InnoDB *which works for
point-in-time recovery and replication slave creation*. Formerly, mysqldump --master-data --single-transaction
used to call in fact mysqldump --master-data, so the dump was not an online dump (took big lock all time of dump).
The only lock which is now taken in this patch is at the beginning of the dump: mysqldump does:
FLUSH TABLES WITH READ LOCK; START TRANSACTION WITH CONSISTENT SNAPSHOT; SHOW MASTER STATUS; UNLOCK TABLES;
so the lock time is in fact the time FLUSH TABLES WITH READ LOCK takes to return (can be 0 or very long, if
a table is undergoing a huge update).
I have done some more minor changes listed in the paragraph of mysqldump.c.
WL#2237 "WITH CONSISTENT SNAPSHOT clause for START TRANSACTION":
it's a START TRANSACTION which additionally starts a consistent read on all
capable storage engine (i.e. InnoDB). So, can serve as a replacement for
BEGIN; SELECT * FROM some_innodb_table LIMIT 1; which starts a consistent read too. 

into mysql.com:/home/my/mysql-4.1

Print position in normal log for Binlog dump

into pcgem.rdg.cyberkinetica.com:/usr/home/acurtis/work/bug6031

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1

    added new variable for ndb port 1186
    changed meaning of ndb_port_base to be default tcp port setting
    changed to use split between port and port_base for ndbcluster
    so that ndb_port and ndb_port_base are propagated to startscript for ndbcluster
    added larger space to pid print
    moved readAndExecute out of CommandInterpreter to avoid linking lib with readline
    added c-api to Ndb_mgmclient
    pass also ndb_port to make

  DROP DATABASE failed because of file ext not in TYPELIB of known extensions.
  General solution - construct a TYPELIB at runtime instead of a static list.

into mysql.com:/home/my/mysql-4.1

into mysql.com:/usr/home/bar/mysql-4.1

into mysql.com:/usr/home/bar/mysql-4.1

into mysql.com:/home/wax/mysql/mysql-4.1mysqltest

the result takes its charset/collation
attributes from the character string,
e.g.  SELECT func(NULL, _latin2'string')
now returns a latin2 result. This is
done by introducing a new derivation
(aka coercibility) level DERIVATION_IGNORABLE,
which is used with Item_null.
2. 'Pure' NULL is now BINARY(0), not CHAR(0).
I.e. NULL is now more typeless.