into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-4.1-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint

into  vajra.(none):/opt/local/work/mysql-5.1-runtime

This will hopefully fix events.test failure on vmware-win32, 
where scheduling is very primitive.

into  vajra.(none):/opt/local/work/mysql-5.1-runtime

Apparently it's the only platform in pushbuild where we 
compile without openssl.

Usage:
  query_sorted <query>;

into  vajra.(none):/opt/local/work/mysql-5.1-c1

Bug#23631 "Events: SHOW VARIABLES doesn't work when mysql.event 
is damaged:

into  siva.hindu.god:/home/tsmith/m/bk/maint/51

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint

Cleanup exit handling

into  vajra.(none):/opt/local/work/mysql-5.1-c1

when there are no up-to-date system tables to support it:
 - initialize the scheduler before reporting "Ready for connections".
   This ensures that warnings, if any, are printed before "Ready for
   connections", and this message is not mangled.
 - do not abort the scheduler if there are no system tables
 - check the tables once at start up, remember the status and disable
   the scheduler if the tables are not up to date.
   If one attempts to use the scheduler with bad tables,
   issue an error message.
 - clean up the behaviour of the module under LOCK TABLES and pre-locking
   mode
 - make sure implicit commit of Events DDL works as expected.
 - add more tests


Collateral clean ups in the events code.

This patch fixes Bug#23631 Events: SHOW VARIABLES doesn't work 
when mysql.event is damaged

into  quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/mrg04/51

When MySQL logged slow query information to a CSV table, it stored the
query_time and lock_time values with an incorrect formula.

If the time was over 59 seconds, this caused incorrect statistics (either the
slow query was not logged, or the time was far from correct).  This change
fixes the method used to store those TIME values in the slow_log table.

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint

   - length($sockdir) >= 80 !!

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-maint

 - length($sockdir) >= 80 !!

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-maint