Use better wording

into  outpost.site:/home/cps/mysql/trees/5.1-runtime-bug9191

which got broken during refactoring.

into  outpost.site:/home/cps/mysql/trees/5.1-runtime-bug9191

into  outpost.site:/home/cps/mysql/trees/5.0-runtime-bug9191

Fixed the tests for case insensitive platforms

into  alik.:/mnt/raid/alik/MySQL/devel/5.1-rt-merged

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-cleanup

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-cleanup

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

into  weblab.(none):/home/marcsql/TREE/mysql-5.1-21114_b

Due to the complexity of this change, everything is documented in WL#3565

This patch is the third iteration, it takes into account the comments
received to date.

into  example.com:/work/mysql-5.1-runtime-bug22830-new

Events: crash with procedure which alters events with function

Post-review CS

This fix also changes the handling of KILL command combined with
subquery. It changes the error message given back to "not supported",
from parse error. The error for CREATE|ALTER EVENT has also been changed
to generate "not supported yet" instead of parse error.
In case of a SP call, the error is "not supported yet". This change
cleans the parser from code which should not belong to there. Still
LEX::expr_allows_subselect is existant because it simplifies the handling
 of SQLCOM_HA_READ which forbids subselects.

into  bodhi.local:/opt/local/work/mysql-5.1-runtime-merge

into  bodhi.local:/opt/local/work/mysql-5.1-runtime-merge

into  bodhi.local:/opt/local/work/mysql-5.0-runtime-merge

into  bodhi.local:/opt/local/work/mysql-5.0-runtime-merge

into  bodhi.local:/opt/local/work/mysql-4.1-runtime

bug#23110  Some NDB tests assert randomly on mixed mode binlog: Don't reset binlog format for NDB binlog injector thread

into  mysql.com:/home/my/mysql-5.1

Fixed some possible fatal wrong arguments to printf() style functions
Initialized some not initialized variables
Fixed bug in stored procedure and continue handlers
(Fixes Bug#22150)

into  mysql.com:/home/cps/mysql/trees/5.1-runtime-bug9191

  bug#21052

into  mysql.com:/home/cps/mysql/trees/5.0-runtime-bug9191

(4.1 version, with post-review fixes)
  
  The fix for another Bug (6439) limited FROM_UNIXTIME() to
  TIMESTAMP_MAX_VALUE which is 2145916799 or 2037-12-01 23:59:59 GMT,
  however unix timestamp in general is not considered to be limited 
  by this value. All dates up to power(2,31)-1 are valid.
  
  This patch extends allowed TIMESTAMP range so, that max
  TIMESTAMP value is power(2,31)-1. It also corrects
  FROM_UNIXTIME() and UNIX_TIMESTAMP() functions, so that
  max allowed UNIX_TIMESTAMP() is power(2,31)-1. FROM_UNIXTIME()
  is fixed accordingly to allow conversion of dates up to
  2038-01-19 03:14:07 UTC. The patch also fixes CONVERT_TZ()
  function to allow extended range of dates.
  
  The main problem solved in the patch is possible overflows
  of variables, used in broken-time representation to time_t
  conversion (required for UNIX_TIMESTAMP).

into  mockturtle.local:/home/dlenev/src/mysql-5.0-hash-2

into  mockturtle.local:/home/dlenev/src/mysql-5.1-merge

Use lazy initialization for Query_tables_list::sroutines hash.
This step should significantly decrease amount of memory consumed
by stored routines as we no longer will allocate chunk of memory
required for this HASH for each statement in routine.

into  trift2.:/MySQL/M51/push-5.1

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0-ndb

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

  remove timeing dependant part of test

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

into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug21915