into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.0

subqry order by server crash": failing DBUG_ASSERT(curr_join == this)
when opening a cursor.
Ensure that for top-level join curr_join == join (always), 
and thus fix the failing assert.
curr_join is a hack to ensure that uncacheable subqueries can be
re-evaluated safely, and should be never different from main join
in case of top-level join.

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.0

into  mysql.com:/home/dlenev/src/mysql-5.0-bg12280

We should not allow FLUSH statement to be executed inside both triggers
and stored functions.

into moonbone.local:/work/mysql-5.0-bug-12340

into  monster.:D:/Work/mysql/mysql-5.0

str_alloc had been added but was not added to mysqlclient and strings
libmysql should have had strings as a dependent.

When PRIMARY KEY is present ha_innobase::cmp_ref() uses it to compare refs.
After comparing part of key it moves pointers to compare next part.
For varchar parts pointers were moved only by length of parts, not including
bytes containig part length itself. This results in wrong comparision and
wrong number of deleted records.

into  mysql.com:/home/dlenev/src/mysql-5.0-is

information_schema causes empty result set" with main tree.

into  mysql.com:/home/dlenev/src/mysql-5.0-is

  Add a forgotten newline to a print

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into  mysql.com:/home/kostja/mysql/mysql-5.0-11909

CURSOR_TYPE_READ_ONLY nested queries corrupt result"

  After merge fix

into  mysql.com:/usr/home/bar/mysql-5.0

into mysql.com:/home/psergey/mysql-5.0-bug12082

result set".

To enable full access to contents of I_S tables from stored functions
or statements that use them, we manipulate with thread's open tables
state and ensure that we won't cause deadlock when we open tables by
ignoring flushes and name-locks.
Building of contents of I_S.TABLES no longer requires locking of tables
since we use use handler::info() method with HA_STATUS_AUTO flag instead
of handler::update_auto_increment() for obtaining information about
auto-increment values. But this also means that handlers have to implement
support for HA_STATUS_AUTO flag (particularly InnoDB needs it).

into  mysql.com:/usr/home/bar/mysql-4.1.b10892

  After review fix

into rurik.mysql.com:/home/igor/mysql-5.0

into  mysql.com:/home/mydev/mysql-5.0-5000

  Correction after manual merge.

into  mysql.com:/home/mydev/mysql-5.0-5000

into mysql.com:/home/psergey/mysql-5.0-bug11869-part3