into  dl145k.mysql.com:/tmp/andrei/5.0.21-bug17284-temp_table

into  mysql.com:/home/alexi/bugs/mysql-5.0-15758

env variable name is fixed.

into  mysql.com:/users/lthalmann/bk/mysql-5.0

Removing the problematic line from include test file.

into  dl145j.mysql.com:/tmp/5.0.21-bug17284-temp_table

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

 innobase_query_caching_of_table_permitted()".
 Applied the patch due to Heikki Tuuri.
 Also removed superfluous #ifdefs.

into mysql.com:/M50/mtr-5.0

into  mysql.com:/usr_rh9/home/elkin.rh9/MySQL/FIXES/5.0.21-bug17284-temp_table

  
     Idea of the fix is for master to send FD event with `created' as 0
     to reconnecting slave (upon slave_net_timeout, no master crash) to avoid destroying temp tables.
     In a case of a connect by slave to the master after its crash temp tables have been already
     cleaned up so that slave can not keep `orphan' temp tables.

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

 skip charset aggregation for order columns

 move test case for bug 14290 to ctype_ucs test

The problem was due to the fact that with --lower-case-table-names set to 1 
the function find_field_in_group did not convert the prefix 'HU' in
HU.PROJ.CITY into lower case when looking for it in the group list. Yet the
names in the group list were extended by the database name in lower case.

into  mysql.com:/home/greenman/workspace-mysql/mysql/bug-5.0-16240

into  mysql.com:/home/psergey/mysql-5.0-bug18237-review

into  april.(none):/home/svoj/devel/mysql/BUG14945/mysql-5.0

counter".

When TRUNCATE TABLE was called within an stored procedure the
auto_increment counter was not reset to 0 even if straight
TRUNCATE for this table did this.

This fix makes TRUNCATE in stored procedures to be handled exactly
in the same way as straight TRUNCATE. We achieve this by rolling
back the fix for bug 8850, which is no longer needed since stored
procedures don't require prelocked mode anymore (and TRUNCATE is
not allowed in stored functions or triggers).

into  shellback.(none):/home/msvensson/mysql/mysql-5.0

as it is now required by mysql_set_character_set()

  Bug#18830 incompatibility new libraries with old server
  Additional 5.0 fix:
  applying the same patch to client.c.

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

  Bug#18830: incompatibility new libraries with old server
  Don't execute SET NAMES with pre-4.1 server.

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

Adding test case to cover queries which worked incorrectly earlier:
Bug#18321: Can't store EuroSign with latin1_german1_ci and latin1_general_ci

  Using local.