into  mysql.com:/extern/mysql/work/bug16303/mysql-5.0

into  mysql.com:/extern/mysql/work/bug16303/mysql-5.0

into  mysql.com:/extern/mysql/work/bug16568/mysql-5.0

into  mysql.com:/space/pekka/ndb/version/my50

into  mysql.com:/space/pekka/ndb/version/my50

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

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

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

into  rurik.mysql.com:/home/igor/mysql-5.0

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

into  mysql.com:/opt/local/work/mysql-5.0-root

  manual adding the fix for bug#15828 which did not automerge

into  mysql.com.:/data/BK/mysql-5.0_15828

into  mysql.com:/opt/local/work/mysql-5.0-root

(No change of functionality)

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

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

When an ambiguous field name is used in a group by clause a warning is issued
in the find_order_in_list function by a call to push_warning_printf.
An expression that was not always valid was passed to this call as the field
name parameter.

into  mysql.com:/extern/mysql/work/bug15011/mysql-5.0

Added comments.

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

  which is no longer repeatable. (Unclear when this was fixed.)

into  mysql.com:/extern/mysql/work/cantrepeat/mysql-5.0

Fix for extra zero in exponent of double values on windows.

A query with a group by and having clauses could return a wrong
result set if the having condition contained a constant conjunct 
evaluated to FALSE.
It happened because the pushdown condition for table with
grouping columns lost its constant conjuncts.
Pushdown conditions are always built by the function make_cond_for_table
that ignores constant conjuncts. This is apparently not correct when
constant false conjuncts are present.

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss162

  Applied innodb-5.0-ss149/162 snapshots.

into  devsrv-b.mysql.com:/space/magnus/my41-bug15302

                               no order by clause
which was fixed by earlier changesets.
The error message is now the more generic "Unknown table ... in field list".