into  maint2.mysql.com:/data/localhome/tsmith/bk/50

into  rama.(none):/home/jimw/my/mysql-5.0-clean

so that 4.1 and 5.0 tests are all in the right place and no tests are duplicated.

into  maint2.mysql.com:/data/localhome/tsmith/bk/50

into  zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint

into  zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint

into  zippy.cornsilk.net:/home/cmiller/work/mysql/no-strange-literals/my50-no-strange-literals

single file is a bad practice.  

 - Don't add the signatures for CRYPTO_* when compiling yaSSL for MySQL

 - Correct bug in perl script that faild to add rename macros for some functions.

into  shellback.(none):/home/msvensson/mysql/mysql-5.0-maint

into  bodhi.local:/opt/local/work/mysql-5.0-14897

into  zippy.cornsilk.net:/home/cmiller/work/mysql/bug04053/my50-bug04053

into  maint2.mysql.com:/data/localhome/tsmith/bk/50

into  maint2.mysql.com:/data/localhome/tsmith/bk/50

into  zippy.cornsilk.net:/home/cmiller/work/mysql/bug04053/my41-bug04053

	event' from master"

Since there is no repeatable test case, and this is obviously wrong, this is
the most conservative change that might possibly work.  

The syscall  read()  wasn't checked for a negative return value for an
interrupted read.  The kernel  sys_read()  returns -EINTR, and the "library" 
layer maps that to return value of -1 and sets  errno  to EINTR.  It's 
impossible (on Linux) for  read()  to set errno EINTR without the return 
value being -1 .

So, if we're checking for EINTR behavior, we should not require that the
return value be zero.

into  maint2.mysql.com:/data/localhome/tsmith/bk/bfx/50

into  bodhi.local:/opt/local/work/mysql-5.0-14897

into  maint2.mysql.com:/data/localhome/tsmith/bk/bfx/41

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

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

into  neptunus.(none):/home/msvensson/mysql/mysql-5.0-maint

 - Use the "%.*b" format when printing prepared and exeuted prepared statements to the log.
 - Add test case to check that also prepared statements end up in the query log
Bug#14346 Prepared statements corrupting general log/server memory
 - Use "stmt->query" when logging the newly prepared query instead of "packet"

  Auto merged

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

length limit", it's superseded by the fix for Bug#16899 "Possible buffer
overflow in handling of DEFINER-clause". Update test results.

into  bodhi.local:/opt/local/work/mysql-5.0-14897

doesn't find the column"

When a user was using 4.1 tables with VARCHAR column and 5.0 server
and a query that used a temporary table to resolve itself, the
table metadata for the varchar column sent to client was incorrect:
MYSQL_FIELD::table member was empty.

The bug was caused by implicit "upgrade" from old VARCHAR to new
VARCHAR hard-coded in Field::new_field, which did not preserve
the information about the original table. Thus, the field metadata
of the "upgraded" field pointed to an auxiliary temporary table
created for query execution.

The fix is to copy the pointer to the original table to the new field.

into  bk-internal.mysql.com:/data0/bk/mysql-5.0-kt

into  polly.local:/home/kaa/src/maint/m50-maint--07OGt

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-bug17591

  - BUG#15934: Instance manager fails to work;
  - BUG#18020: IM connect problem;
  - BUG#18027: IM: Server_ID differs;
  - BUG#18033: IM: Server_ID not reported;
  - BUG#21331: Instance Manager: Connect problems in tests;

The only test suite has been changed
(server codebase has not been modified).