Fix for storing negative values in decimal fields
Fix for FLUSH TABLE with HANDLER

into mysql.com:/my/mysql-4.1

Fixed compiler warnings (IRIX C compiler and VC++)

into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1

into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1

into mashka.mysql.fi:/home/my/mysql-4.1

Add missing file to VC++ project

into mysql.com:/home/mysql_src/mysql-4.1

has (in mysql-test-run) a slave-net-timeout=10. So the 'sleep 1' below
was converted in 'sleep 10', so slave thought that connection was down,
so reconnected, so got an additional (fake) Rotate event, which shifted
the positions displayed by SHOW SLAVE STATUS.

into serg.mylan:/usr/home/serg/Abk/mysql-4.0

minor fixups: more verbose on "no memory" errors - report requested size, avoid flushing rec buffer to a file that is closed and deleted already (on got_error=1)

   setting LIBS to include @openss_libs@ (BUG#1652)

into mashka.mysql.fi:/home/my/mysql-4.1

Changed ~Item_func_in() to call cleanup() (to fix memory leak)
Fixed test_multi_statements() test in client_test

into bar.mysql.r18.ru:/usr/home/bar/mysql-4.1

  There were errors in cp850: in unicode, ctype and sort arrays

more user variable tests

into mysql.com:/space/my/mysql-4.1

into sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1

into mysql.com:/space/my/mysql-4.1

into mysql.com:/bk/mysql-4.1

into sanja.is.com.ua:/home/bell/mysql/bk/work-used_tables-4.1

into mysql.com:/space/my/mysql-4.1

into sanja.is.com.ua:/home/bell/mysql/bk/work-used_tables-4.1

into sanja.is.com.ua:/home/bell/mysql/bk/work-delete-4.1

into mysql.com:/home/mysql_src/mysql-4.0

    "CHANGE MASTER makes SQL thread restart from coordinates of I/O thread".
    So, in CHANGE MASTER:
    when it seems reasonable that the user did not want to discontinue
    its replication (i.e. when he is not specifying host or port or master_log_file
    or master_log_pos; this will be documented), set the coordinates of the
    I/O thread to those of the SQL thread. This way, the SQL thread will see
    no discontinuity in the relay log (i.e. will skip no events), because
    the I/O thread will fill the brand new relay log with the events which
    are just after the position where the SQL thread had stopped
    (before CHANGE MASTER was issued).
    And a new test for this bug.