This saves one byte per Query_log_event on disk compared to 5.0.[0..3]. Compatibility problems with 5.0.x where x<4
are explained in the comments in log_event.cc. Putting back s/my_open(O_TRUNC)/(my_delete+my_create) change which had
been wiped away by somebody doing a wrong 4.1->5.0 merge (which happened just
before 5.0.3 :( ). Applying it to new events for LOAD DATA INFILE.
If slave fails in Execute_load_query_log_event::exec_event(),
don't delete the file (so that it's re-usable at next START SLAVE).
And (youpi!) fix for BUG#3247 "a partially completed LOAD DATA INFILE is not
executed at all on the slave" (storing an Execute_load_query_log_event
to binlog, with its error code, instead of Delete_file_log_event).

  result update (default value changed from 4.1 to 5.0)

into quadita2.mysql.com:/nfstmp1/guilhem/mysql-5.0-4ita

 and Bug#9159 "Server crash during mysql_stmt_close".
The patch adds support for single-row result sets in cursors.

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

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

server" to the test suite, the bug is no longer repeatable.

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

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

"Server crashes when running out of connections"

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

into quadita2.mysql.com:/nfstmp1/guilhem/mysql-4.1-4ita

into mysql.com:/media/sda1/mysql/mysql-5.0-6282

(the bug itself is no longer repeatable).

"After Monty's review" changes to the fix for BUG#8325 "Deadlock in replication thread stops replication":
s/sleep/safe_sleep (thread safe); sleep 0/1/2/3/4/5/5/5 (get slave less late);
no message on error log (deadlock is too common sometimes), a global counter
instead (SHOW STATUS LIKE 'slave_retried_transactions').
Plus a fix for libmysql/Makefile.shared

    report correct errror in MODE_NO_AUTO_CREATE_USER
    cleanup
after merge fixes

into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-5.0

into kite-hub.kitebird.com:/src/extern/MySQL/bk/merge-5.0

  Fix typo.

  Fix bug #9314 in InnoDB true VARCHAR: InnoDB stored the 'position' of a row wrong in a column prefix primary key index; this could cause MySQL to complain 'ERROR 1032: Can't find record in ...' in an update of the primary key, and also some ORDER BY or DISTINCT queries

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

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

applications with embedded server to connect to external servers too.
(required for Connector/OO.org)

into neptunus.(none):/home/msvensson/mysql/mysql-4.1

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

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

into mysql.com:/data0/mysqldev/jimw/mysql-5.0-build

the row type is dynamic (For 4.1 tables old 'VARCHAR' fields are converted to
true VARCHAR in the next ALTER TABLE)
      
This ensures that one can use MySQL 5.0 privilege tables with MySQL 4.1.

(Fix imported from main 5.0 tree to 5.0.3 build tree.)

into mysql.com:/data0/mysqldev/serg/m50b

fixed my_charpos() call in Field_varstring::get_key_image

into mysql.com:/data0/mysqldev/jimw/mysql-5.0-build