into tetra.spaceapes.com:/home/jcole/bk/mysql

do val_int() on their arguments before starting the computation. 
Similar fixes are need for +-* and probably several other but I want
to make sure Monty is fine with my fix approach before changing a lot
of code. 

Amazingly,
this bug is not as critical as you would expect since very few functions do val_int()
on their arguments ( from_unixtime(), sec_to_time()), and those not
very frequently perform a computation on their floating point arguments.
which is probably why no one has yet reported this bug. Another 
possibility is that the result is usually wrong by no more than 5%,
which makes it hard to catch it. I found it when trying to compute mile
splits for 30:47 10K - it told me 5:07, and I knew it was wrong because
5:00 mile gives you 31:08. However, if I had not run as many 10K races,
I would have easily believed that 30:47 10K is a 5:07 mile pace and 
would not have noticed the bug.

into mysql.sashanet.com:/home/sasha/src/bk/mysql

  Fixed contributed software link

  Added mirror in Hong Kong

into mysql.sashanet.com:/home/sasha/src/bk/mysql

Replaced @strong{MySQL AB} with MySQL AB

row0sel.c	Fix a memory freeing bug when a row which contains an externally stored long field in the middle of the row is fetched in a SELECT
srv0start.c	Allow drive name followed by a ':' in a data file path
ha_innobase.cc	Allow drive name followed by a ':' in a data file path

into mysql.sashanet.com:/home/sasha/src/bk/mysql

Added record_rnd_buffer
Added --safe-user-create
Fix for ALTER TABLE RENAME on windows

Portability fixes
Fixed problem when giving wrong arguments to myisam_recover
Fix to remove warnings when using purify

enabled or not.

and sql-mode options.