deadlock in MYSQL_LOG::new_file()
style fixes

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

into mysql.com:/space/pekka/ndb/version/my50-ndb

into mysql.com:/home/svoj/devel/mysql/stddev-mysql-5.0

into mysql.com:/space/pekka/ndb/version/my50-ndb

  fix error code

into mysql.com:/usr/local/home/marty/MySQL/test/mysql-5.0-ndb

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

Temporary patch to remove some warnings

  Fix wrong spelling

  Make InnoDB-5.0.3 to process log records of 4.1 undo log header create and reuse just like in 4.1; storing XID to the start of the undo log is a separately logged operation; this conforms to Rule 3 of InnoDB redo logging

This bug is also known as WL#1639.

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

(Found during build process)

  Another multi result statement added.
  Note: No test case, as it's not possible to get a deterministic result from this.

into mysql.com:/home/pem/work/mysql-5.0

into mysql.com:/usr/local/home/marty/MySQL/test/mysql-5.0-ndb

  Have to thd->set_time() before each substatement execution, to make
  current_time() et al return different times within the same procedure.

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/jonas/src/mysql-5.0

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

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

  More explicit naming of variables

into mysql.com:/usr/local/home/marty/MySQL/test/mysql-5.0-ndb

Previously we only stored the first given error (the error sent to the client)

into zim.(none):/home/brian/mysql/mysql-5.0

Funny sometimes how things work when in reality you would think it would crash pretty hard :)

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

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

  Wait some for all nodes to get connected