into  mysql.com:/home/svoj/devel/mysql/BUG24342/mysql-5.1-engines

into  mysql.com:/home/svoj/devel/mysql/BUG24342/mysql-5.0-engines

into  mysql.com:/home/svoj/devel/mysql/BUG24342/mysql-4.1-engines

into  mysql.com:/home/svoj/devel/mysql/BUG25951/mysql-5.1-engines

into  mysql.com:/home/svoj/devel/mysql/BUG25951/mysql-5.0-engines

into  mysql.com:/home/svoj/devel/mysql/BUG27516/mysql-5.1-engines

When a table status is requested by statement like SHOW TABLE
STATUS and there is another statement (e.g. DELETE) sets
number of records to 0 concurrently, we may get division by
zero error, which crashes a server.

This is fixed by using thread local variable x->records instead
of shared info->state->records when we check if it is zero and
divide by it.

IGNORE/USE/FORCE INDEX hints were honored when choosing FULLTEXT
index.

With this fix these hints are ignored. For regular indexes we may
perform table scan instead of index lookup when IGNORE INDEX was
specified. We cannot do this for FULLTEXT in NLQ mode.

MERGE engine may return incorrect values when several representations
of equal keys are present in the index. For example "groß" and "gross"
or "gross" and "gross " (trailing space), which are considered equal,
but have different lengths.

The problem was that key length was not recalculated after key lookup.

Only MERGE engine is affected.

into  mysql.com:/home/kent/bk/tmp4/mysql-5.1-engines

into  mysql.com:/home/kent/bk/tmp4/mysql-5.0-engines

into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1

into  xiphis.org:/home/antony/work2/mysql-5.1-engines.merge

into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user

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

into  xiphis.org:/home/antony/work2/mysql-5.0-engines.merge

into  xiphis.org:/home/antony/work2/mysql-5.1-engines.merge

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  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user

into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user

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

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

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

  Bug #26591  Cluster handler does not set bits in null bytes correctly: Improved comments
ha_ndbcluster_binlog.cc:
  Bug #26591  Cluster handler does not set bits in null bytes correctly: Using empty_record() instead of bzero

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  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-single-user

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