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

mysqldump.result is wrong, will need to be cleaned up.

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

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

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

Fixes bad merge.

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

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

single file is a bad practice.  

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

 - Wait for ndb_mgmd with timeout

Add check in 'spawn_impl' that we are not trying to span when the path to the executable is empty or undefined

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

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

into  zippy.cornsilk.net:/home/cmiller/work/mysql/merge/mysql-5.1

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

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/51

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

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

into  neptunus.(none):/home/msvensson/mysql/bug21813/my51-bug21813

 - 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"

CMake versions > 2.4 allow linking to STATIC or SHARED libraries only.

into  gbichot3.local:/home/mysql_src/mysql-5.1-maint

into  polly.local:/home/kaa/src/maint/m51-new-maint--07OGx

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

into  gbichot3.local:/home/mysql_src/mysql-5.1-maint

and its duplicate BUG#19057 "Test 'rpl_row_func003' fails on SuSE SLES9 x86".
It was an assertion failure, only in debug builds, not present
in released versions (nothing to document).
It happened when doing SHOW TABLE STATUS on an InnoDB table
having an auto_increment column, right after creating the table.
The test which would have caught this problem was disabled in 
mid-April for another reason (how much I like tests disabled for
months...).

into  lamia.home:/home/timka/mysql/src/5.1-bug-21456

into  zippy.cornsilk.net:/home/cmiller/work/mysql/merge/mysql-5.1

into  rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-5.1-new-maint_21527

    
init_dumping now accepts a function pointer to the table or view specific init_dumping function.  This allows both tables and views to use the init_dumping function.

into  salvation.intern.azundris.com:/home/tnurnberg/mysql-5.1-maint