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

  New privilege CREATE USER (CREATE_USER_ACL, Create_user_priv) added
grant2.test:
  new tests (mostly backported from jani's patch)
system_mysql_db.result, sp.result, grant2.result, grant.result:
  results updated

into mysql.com:/Users/kent/mysql/bk/mysql-5.0-build

  InnoDB needs longer start time for second slave on slow hosts

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

included before any other include) was hidden from me.

  5.0.3 is a beta

into mysql.com:/Users/kent/mysql/bk/mysql-5.0-build

  Added 'proc' and 'procs_priv' tables, updated others

into mysql.com:/Users/kent/mysql/bk/mysql-5.0-build

(Change done by Ramil and sent via IRC)

  Made --timer work
mtr_cases.pl:
  Added option --reorder to get less server restarts
mysql-test-run.pl:
  Added option --reorder to get less server restarts
  Moved do_before_start_master() not to remove binlog files unless restarted
  Made --timer work
  Slave was incorrectly writing log to error log

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

"Warnings on 'drop procedure' platform-specific").

In mysqltest we should not issue "SHOW WARNINGS" until we have not 
read results from all statements in multi-statement.

Otherwise such "SHOW WARNINGS" will either cause "Packets out of order"
error and thus will ruin current connection (but we may not notice this as
it happened in sp.test because we ignore errors from such auxilary
SHOW WARNINGS and use auto-reconnecting connections) or will
succeed but consume first packet from next statement in multi-statement
sequence (this happens if "SHOW WARNINGS" is issued when this packet
is already received by client. Packet is thrown away by net_clear()
call which is issued when "SHOW WARNINGS" is sent to server).

In our case sp.test failed because usually we had first situation
but sometimes second situation occured causing warning to pop-up.

been killed.

(patch from lenz, reapplied by jimw)

Windows to call CreateFileMapping() with correct arguments, and
propogating the introduction of query_id_t to everywhere query ids are
passed around. (Bug #8826)

  Disabled old feature to disable test cases

into mysql.com:/M50/build-5.0.3

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

  transactional test removed
sp_trans.test, sp_trans.result:
  new file

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