into hundin.mysql.fi:/home/heikki/mysql-5.0

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

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

into zim.(none):/home/brian/mysql/mysql-5.0

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

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

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

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

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

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

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

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

into sinisa.nasamreza.org:/mnt/work/petica

into sinisa.nasamreza.org:/mnt/work/petica

  Fix for a bug with test failing with Classic.

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

  Revert the change to the space padding of BLOB and TEXT in comparisons; we cannot change the sorting order, because that would make old tables to appear corrupt; better to change LIKE 'a%' processing in MySQL, so that the lower end of the search interval would be 'a', not 'a       '

into hundin.mysql.fi:/home/heikki/mysql-5.0

into zim.(none):/home/brian/mysql/mysql-5.0

  Update endspace.result now that InnoDB pads BLOBs properly with spaces in comparisons

  Fix that 'a' LIKE 'a%' was not true for an InnoDB BLOB or TEXT type column prefix index search: InnoDB assumed that the BLOB and TEXT should not be padded with space in comparisons; this bug is also in 4.1; it may have worked in 4.1 because MySQL may have asked there for strings >= 'a', while in 5.0 it asks for strings >= 'a        '

  Someone has fixed the calculation of length() for a returned InnoDB VARCHAR value: update endspace.result to have the correct value length('teststring') == 10

into gluh.mysql.r18.ru:/home/gluh/MySQL-MERGE/mysql-5.0

into gluh.mysql.r18.ru:/home/gluh/MySQL-MERGE/mysql-5.0

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

First one is related to Bug#7905. One should not be allowed to
create new user with password without UPDATE privilege to
MySQL database. Furthermore, executing the same GRANT statement
twice would actually crash the server and corrupt privilege database.

Other bug was that one could update a column, using the existing
value as basis to calculate the new value (e.g. UPDATE t1 SET a=a+1)
without SELECT privilege to the field (a in the above example)

Fixed tests grant.pl and grant2, which were wrong.

into zim.(none):/home/brian/mysql/mysql-5.0