into  mysql.com:/home/kent/bk/main/mysql-5.1

into  radha.patg.net:/Users/patg/mysql-build/mysql-5.1-arch-merge

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-arch

into  radha.patg.net:/Users/patg/mysql-build/mysql-5.1-arch-merge

* Various windows errors fixed
* Increased max key length for federated

into  trift2.:/MySQL/M51/tmp-5.1

into  trift2.:/MySQL/M51/push-5.1

into  siva.hindu.god:/usr/home/tim/m/bk/51-build

into  siva.hindu.god:/usr/home/tim/m/bk/51-build

into  bk-internal.mysql.com:/data0/bk/mysql-5.0-build

fixing pushbuild warnings and errors

into  trift2.:/MySQL/M51/push-5.1

into  trift2.:/MySQL/M50/clone-5.0

into  trift2.:/MySQL/M50/clone-5.0

into  trift2.:/MySQL/M50/push-5.0

into  kahlann.erinye.com:/home/df/mysql/build/mysql-5.0-release

into  kahlann.erinye.com:/home/df/mysql/build/mysql-5.0-release

into  siva.hindu.god:/usr/home/tim/m/bk/50-build

into  siva.hindu.god:/usr/home/tim/m/bk/50-build

into  siva.hindu.god:/usr/home/tim/m/bk/50-release

more similar to my_strtod() (and maybe even a bit faster due
to less floating point divisions).

This should at least partially fix Bug #23260 for DECIMALs
with a moderate number of total digits.

InnoDB timeout behavior (Bug #24200)

Handling of large signed/unsigned values was not consistent, so some string functions could return bogus results.
The current fix is to simply patch up the val_str() methods for those string items.
It would be good clean this code up in general, to make similar problems much harder to make.  This is left as an exercise for the reader.

into  kahlann.erinye.com:/home/df/mysql/build/mysql-5.0-release

into  kahlann.erinye.com:/home/df/mysql/build/mysql-5.0-build-work

The final testcase needing new error codes. Really.

into  mysql.com:/data0/mysqldev/my/build-200612151202-5.0.32/mysql-5.0-release

into  radha.patg.net:/Users/patg/mysql-build/mysql-5.1-arch-clean

into  siva.hindu.god:/usr/home/tim/m/bk/50-build

Applied innodb-5.0-ss1040 and innodb-5.0-ss1099 snapshots.

Bugs fixed:
- Bug #21468: InnoDB crash during recovery with corrupted data pages: XA bug?
- Bug #24299: Identifiers in foreign keys cannot contain U+0160, U+0360, ..., U+FF60
- Bug #24386: Performance degradation caused by instrumentation in mutex_struct
- Bug #24712: SHOW TABLE STATUS for file-per-table showing incorrect time fields