into  dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE2/mysql-5.1-opt

into  mysql.com:/home/hf/work/thfix/my51-thfix

into  mysql.com:/home/hf/work/thfix/my50-thfix

into  mysql.com:/home/hf/work/thfix/my51-thfix

into  mysql.com:/home/hf/work/thfix/my50-thfix

the problem is that client tools are compiled with UNDEF_THREADS_HACK
flag, and my thread-related additions to the mysqltest.c can't be compiled.
Easy solution is to disable these in not-embedded case completely.

into  dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.1-opt

into  rakia.gmz:/home/kgeorge/mysql/autopush/B24156-5.0-opt

           statements
Currently the optimizer evaluates loose index scan only for top-level SELECT
statements
Extend loose index scan applicability by :
 - Test the applicability of loose scan for each sub-select, instead of the
   whole query. This change enables loose index scan for sub-queries.
 - allow non-select statements with SELECT parts (like, e.g. 
   CREATE TABLE .. SELECT ...) to use loose index scan.

into  rakia.gmz:/home/kgeorge/mysql/autopush/B11927-5.0-opt

 When implicitly converting string fields to numbers the 
 string-to-number conversion error was not sent to the client.
 Added code to send the conversion error as warning.
 
 We also need to prevent generation of warnings from the places
 where val_xxx() methods are called for the sole purpose of updating
 the Item::null_value flag.
 To achieve that a special function is added (and called) : 
 update_null_value(). This function will set the no_errors flag and
 will call val_xxx(). The warning generation in Field_string::val_xxx()
 will use the flag when generating the conversion warnings. 

  dummy commit to trigger pushbuild

Removed warnings from mysqltest scripts

Fixed that test_thr_alarm works

Ensure that my_size_t is always unsigned (to get predictiable results from system to system)
Removed some %lld, as these are not portable

into  dl145s.mysql.com:/data0/bk/team_tree_merge/MERGE/mysql-5.1-opt

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

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

Added missing DBUG_RETURN statements (in mysqldump.c)
Added missing enums
Fixed a lot of wrong DBUG_PRINT() statements, some of which could cause crashes
Removed usage of %lld and %p in printf strings as these are not portable or produces different results on different systems.

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-marvel

Load shared libraries from zlib (fixed that mysql-test-run.pl didn't work on some Solaris boxes)
Added connect timeout to test to make im_daemon_life_cycle more predictable

Disabling debug printouts for valgrind builds that print unallocated memory.

Fixed that --valgrind works again with mysql-test-run.sh
Extended error messages when loosing connection during mysql_real_connect()

Removing valgrind memory checks from code.

Patch to fix valgrind warning that uninitialized bytes were written. 
The warning was caused by set_default(), which assumes that the field pointer is pointing
into record[0], while all other functions honors the move_field_offset().

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

into  macbook.gmz:/Users/kgeorge/mysql/work/merge-5.1-opt

into  macbook.gmz:/Users/kgeorge/mysql/work/merge-5.1-opt

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

Moved .progress files into the log directory
Moved 'cluster' database tables into the MySQL database, to not have 'cluster' beeing a reserved database name
Fixed bug where mysqld got a core dump when trying to use a table created by MySQL 3.23
Fixed some compiler warnings
Fixed small memory leak in libmysql
Note that this doesn't changeset doesn't include the new mysqldump.c code required to run some tests. This will be added when I merge 5.0 to 5.1

into  romeo.(none):/home/bk/memcheck-mysql-5.1

Removing DBUG_DUMP printouts for valgrind builds since they trigger warnings.
Removing valgrind memory checks completely.
Removing bzero() of record when opening table that was added earlier.

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

disable filling of I_S tables for EXPLAIN

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

(Mostly in DBUG_PRINT() and unused arguments)
Fixed bug in query cache when used with traceing (--with-debug)
Fixed memory leak in mysqldump
Removed warnings from mysqltest scripts (replaced -- with #)

into  romeo.(none):/home/bk/memcheck-mysql-5.1

Fix to correct behaviour of find_and_fetch_row() for tables that have primary keys stored
in storage engines that support the fast method to fetch rows given a primary key. The
method uses position() to retrieve the key for a given record and rnd_pos() to position
the internal "cursor" at the row. Rnd_pos() returns the found record in table->record[0],
so the record has to be moved to table->record[1] for further processing after calling
find_and_fetch_row().