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

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

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

into hundin.mysql.fi:/home/marko/k/mysql-5.0

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

Can't repeat information_schema test failure
Fix for lowercase_table3 only

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

  Fix a glitch reported by Guilhem: release the memory allocated for innodb_internal_... if innobase_init() fails; cleanups: in ha_innodb, you should use the InnoDB formatting style for the source code

suggested in review by Heikki.

  Fix memory corruption bug reported by Georg Richter: if one created a table whose primary key contained at least 2 column prefixes, that could corrupt the memory heap of prebuilt_t

into mysql.com:/Users/kent/mysql/bk/mysql-5.0-compile

into deer.(none):/home/hf/work/mysql-5.0.clean

into hundin.mysql.fi:/home/marko/mysql-5.0

into mysql.com:/home/mydev/mysql-4.1-bug8306

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

  Adjusted results of the test case for bug #7520 for 4.1.

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

  Added a test case for bug #7520.
table.cc:
  Fixed bug #7520.
  The bug was caused by a wrong calculation of the field max_key_length for
  a TABLE structure when there was an index on a blob field.

Set of fixes requested by Kent in IRC. Tested (except the windows changes since I am trusting Kent...). No windows compiles here folks...

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

binlog-do-db or binlog-ignore-db are in effect.   (In the future 5.1? 5.0? I think 
each statement should be verified against the filtering criteria based on the database
it *uses* and not the *current* one.  But, right now the *current* database is what 
counts according to the semantics of the manual.)

into mysql.com:/home/bk/b7853-mysql-5.0

It was a thread stack overrun.
IA64 had its own stack size section already.
Enlarged its default stack size from 192K to 256K.

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

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