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

into  pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint

Mark one more test as needing binlog

into  pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint

into  pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint

 - Additional tests in 5.1 that need binlog
 - Mark more test to need binlog

into  pilot.(none):/data/msvensson/mysql/bug28369/my51-bug28369

 - Turn on binlog only for tests that need it
 - Skip those tests if --skip-binlog is used

into  xp.:C:/work/mysql-5.1-new-maint

into  xp.:C:/work/mysql-5.0-maint

The events were not being opened in the global namespace.

into  pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint

into  pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint

 - Skip test if the mysqld to test is not started from MYSQLTEST_VARDIR

into  mysql.com:/home/ram/work/b28806/b28806.5.1

Problem: getting an autoincrement value for a partition table in the ::info() method we call
the get_auto_increment() for all partitions. That may cause a problem for at least MyISAM
tables that rely on some table state (in this particular case table->naxt_nuber_field is 
set to 0 in the mysql_insert() and we get a crash). 
Moreover, calling get_auto_increment() is superfluous there.

Fix: use ::info(HA_STATUS_AUTO) calls to get autoincrement values for partitions instead of
get_auto_increment() ones in the ha_partition::info().

into  polly.local:/home/kaa/src/maint/mysql-5.1-maint

into  polly.local:/home/kaa/src/maint/mysql-5.1-maint

This is to fix PB failures introduced by the patch for bug #28895.

into  pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint

into  pilot.(none):/data/msvensson/mysql/bug28690/my51-bug28690

 - Only use the "hack for bug in NTPL" if using NTPL, by dynamically
   checking the thd_lib_detected flag

into  pilot.(none):/data/msvensson/mysql/mysql-5.1-new-maint

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint

into  pilot.(none):/data/msvensson/mysql/mysql-4.1-maint

into  polly.local:/home/kaa/src/maint/mysql-5.0-maint

into  polly.local:/home/kaa/src/maint/mysql-5.1-maint

  The patch for WL 1563 added a new duplicate key error message so that the
  key name could be provided instead of the key number. But the error code
  for the new message was used even though that did not need to change.

  This could cause unnecessary problems for applications that used the old
  ER_DUP_ENTRY error code to detect duplicate key errors.

into  polly.local:/home/kaa/src/maint/bug28895/my51-bug28895

  Add another exception to the acceptable mysqld errors, for test case for bug 28436

  Post-merge fix warning

  Post-merge fix (byte -> uchar)