- when connecting to a mgm server as a transporter, create a NdbMgmHandle
  - over this mgm handle, report the dynamic ports
  - then turn it into a transporter
- this will re-report dynamic ports to mgmds when they restart (as we'll have to
set up our transporter again). This will also report it to all mgmds (as we'll
have transporters to all of them).

into mysql.com:/home/jonas/src/mysql-5.0-ndb

    + removed double check for invalid socket

into mysql.com:/home/jonas/src/mysql-5.0-ndb

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-5.0-ndb

into mysql.com:/home/jonas/src/mysql-5.0-ndb

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-4.1

into mysql.com:/home/kostja/work/mysql-5.0-root

into mysql.com:/home/jonas/src/mysql-5.0-ndb

  increased timeout as it is exceeded every now and then giving erroneous indication on error

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/kostja/work/mysql-5.0-root

reset mysql->net.last_error": the solution is to clear
MYSQL->net error before performing COM_CLOSE: if the call
succeeds, the connection is usable for other statements.
More comprehensive fix is to clear MYSQL->net for all
recoverable errors at the time they happen, it will be
implemented in 5.0 as it introduces incompatibility in behavior.

into neptunus.homeip.net:/home/msvensson/mysql/mysql-5.0

After merge fixes
Don't give duplicate warnings for some ::store() functions

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

into mysql.com:/home/jonas/src/mysql-5.0

into mysql.com:/home/jonas/src/mysql-4.1

into mysql.com:/home/jonas/src/mysql-5.0

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

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

This removes a (small) memory leak.

into mysql.com:/home/jonas/src/mysql-5.0-ndb

into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1