(Found during build process)

Previously we only stored the first given error (the error sent to the client)

into ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0

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

1) If my.cnf is found in datadir and basedir, give a warning and use the
   one in basedir.
2) If my.cnf is found in datadir, use it, but give a warning.
3) No warning if my.cnf is in basedir.

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

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

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

into ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0

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

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

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

  Activate Unicode collations in Windows version.

        bug #7215: information_schema: columns are longtext instead of varchar

The problem was in different representations of double variables depending on
platform/compiler/compile options. In some cases double variables are represented by
64 bits (while in memory), or by 80 bits (while in FPU register). As a result equal
values are not considered "==". As many sources point out,  doubles should not be
compared by '==' for this reason. This fix subtracts the scaled minimal double
value X such that 1 + X != 1, to ensure that the inequality holds in any case.

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

   make sure transporter connections are close early in shutdown

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

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

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

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

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

In Item_cache_decimal::store(item) the call item->val_decimal_result() 
returns NULL if the passed item has an SQL null value. Don't try copying
NULL into Item_cache_decimal::val in this case.

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