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

(No really critical errors found, but a few possible wrong results)

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

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

  Check if node == NULL, which means we are outside tablespace bounds, and print a big fatal error message

into hundin.mysql.fi:/home/heikki/mysql-4.1

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:/usr/home/bar/mysql-4.1-again

  Bug#7997 Add implicit --skip-set-charset when mysqldump from 4.0 server w/ 4.1 client

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

  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:/usr/home/ram/work/4.1.b4802

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

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 :)

  Wait some for all nodes to get connected

mysql-test-run runs with --sleep=10; otherwise GET_LOCK() times out
before being killed so we get 0 instead of NULL. Verified that it
works on our powermacg5 where the test was failing.

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

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