into  mysql.com:/home/timka/mysql/src/5.0-bug-12943

into  mysql.com:/usr/home/bar/mysql-5.0

  Adding esperanto collation

into dl145c.mysql.com:/home/ndbdev/tomas/mysql-5.0

corrected typo in ndb Parser

into  mysql.com:/users/lthalmann/bk/mysql-4.1-magnus

into  mysql.com:/usr/home/ram/work/5.0.b12917

into  mysql.com:/usr/home/ram/work/5.0.b12917

into  mysql.com:/usr/home/bar/mysql-5.0.b12891

into mysql.com:/home/gluh/MySQL/Merge/5.0

into  mysql.com:/usr/home/ram/work/5.0.b12917

into  mysql.com:/usr/home/bar/mysql-5.0.b12891

to eliminate nondeterminism in slave start

into  mysql.com:/usr/home/ram/work/5.0.b12917

into  eel.(none):/home/jonas/src/mysql-5.0-push

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

into  mysql.com:/usr/home/ram/work/5.0.b12917

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

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

Repair of condition pushdown after Item_func_between/in objects now directly represent NOT BETWEEN/IN expressions (ChangeSet@1.2402.1.1)

into  mysql.com:/home/timka/mysql/src/5.0-dbg

into  mysql.com:/users/lthalmann/bk/mysql-4.1-magnus

into  a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-5.0

into  a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-4.1

into  eel.(none):/home/jonas/src/mysql-5.0-push

into  frost.snake.net:/Volumes/frost2/MySQL/bk/mysql-5.0

into  mysql.com:/users/lthalmann/bk/mysql-5.0

  Fix typo.

into  eel.(none):/home/jonas/src/mysql-5.0-push

into  snake-hub.snake.net:/src/extern/MySQL/bk/mysql-5.0

  Fix some comments.

into  a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-4.1

The problem was that in the first production in rule 'join_table', that
processes simple cross joins, the parser was processing the second join operand
before the first one due to unspecified priorities of JOINs. As a result in the
case of cross joins the parser constructed a tree with incorrect nesting:
the expression "t1 join t2 join t3 on some_cond" was interpreted as
"t1 join (t2 join t3 on some_cond)" instead of
"(t1 join t2) join t3 on some_cond".
Because of this incorrect nesting the method make_join_on_context picked an
incorrect table as the first table of the name resolution context.

The solution assignes correct priorities to the related production.

into mysql.com:/home/psergey/mysql-5.0-merge