into mysql.com:/home/cps/mysql/devel/im-fix-review

into mysql.com:/home/cps/mysql/trees/mysql-5.0

Recommited, as I made a typo in the previous patch myself =)

into mysql.com:/home/mysql_src/mysql-5.0-xa

into mysql.com:/home/mysql_src/mysql-5.0-xa

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

into pcgem.rdg.cyberkinetica.com:/var/db/bk/work-acurtis/bug4445.2

into pcgem.rdg.cyberkinetica.com:/var/db/bk/work-acurtis/bug4445.2

into pcgem.rdg.cyberkinetica.com:/var/db/bk/work-acurtis/bug4445.1

  Make a more informative platform info for Windows

into mysql.com:/home/pem/work/mysql-5.0

into mysql.com:/space/pekka/ndb/version/my41-1.2154.30.2

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

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

into rurik.mysql.com:/home/igor/dev/mysql-4.0-0

  Added a test case for bug #8392.
sql_delete.cc:
  Fixed bug #8392.
  The bug caused a crash for a delete statement with ORDER BY
  that explicitly referred to the modified table.

into mysql.com:/M41/mysql-4.1

Since placement operator delete called only if exception was thrown in
constructor and we don't use exceptions in MySQL, there is no sense to
do anything in String::delete(void *ptr_arg, MEM_ROOT *mem_root).

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