into  polly.local:/home/kaa/src/maint/mysql-5.1-maint

This is for bug #28121.

into  polly.local:/home/kaa/src/maint/bug28121/my51-bug28121

When storing a large number to a FLOAT or DOUBLE field with fixed length, it could be incorrectly truncated if the field's length was greater than 31.

This patch also does some code cleanups to be able to reuse code which is common between Field_float::store() and Field_double::store().

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-new-maint

 - Add checks to make sure net has a vio assigned
 - For example bootstrap will create a fake "net" with vio
   set to 0 

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-new-maint

Test for bug #26842 moved to a separate file as it uses 'show binlog events' and fails with --binlog-format=row.

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-new-maint

 - Make the two "my_net_set*" function only visible when included
   from my_global.h

into  mysql.com:/home/ram/work/b26842/b26842.5.0

into  mysql.com:/home/ram/work/b26842/b26842.5.1

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-new-maint

between 5.0 and 5.1 and thus missed the merge

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-new-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint

into  pilot.blaudden:/home/msvensson/mysql/bug26664/my51-bug26664

into  mysql.com:/home/ram/work/b28464.new/b28464.new.5.0

into  mysql.com:/home/ram/work/b28464.new/b28464.new.5.1

into  mysql.com:/home/ram/work/b26842/b26842.5.1

bug #26842: master binary log contains invalid queries - replication fails
bug #12826: Possible to get inconsistent slave using SQL syntax Prepared Statements

Problem:  
binlogging PS' we may produce syntacticly incorrect queries in the binlog replacing 
some parameters with variable names (instead of variable values).
E.g. in the reported case of "limit ?" clause: replacing "?" with "@var"
produces "limit @var" which is not a correct SQL syntax. 
Also it may lead to different query execution on slave if we
set and use a variable in the same statement, e.g.
"insert into t1 values (@x:=@x+1, ?)"

Fix: make the stored statement string created upon its execution use variable values
(instead of names) to fill placeholders.

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-new-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.1-new-maint

into  pilot.blaudden:/home/msvensson/mysql/mysql-5.0-maint

into  pilot.blaudden:/home/msvensson/mysql/bug27438/my51-bug27438

 - The "mysql client in mysqld"(which is used by
   replication and federated) should use alarms instead of setting
   socket timeout value if the rest of the server uses alarm. By
   always calling 'my_net_set_write_timeout'
   or 'my_net_set_read_timeout' when changing the timeout value(s), the
   selection whether to use alarms or timeouts will be handled by
   ifdef's in those two functions. 
 - Move declaration of 'vio_timeout' into "vio_priv.h"

into  mysql.com:/home/ram/work/b28509/b28509.5.0

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

into  shellback.(none):/home/msvensson/mysql/mysql-4.1-maint

 - Check that filemode was set to 0000

into  mysql.com:/home/ram/work/b28509/b28509.5.0

into  mysql.com:/home/ram/work/b28509/b28509.5.1

into  mysql.com:/home/ram/work/b23810/b23810.5.1

We access some variable values using casts like *(long *) buff
that may cause crashes on some platforms (e.g. solaris 64) if buff is
not properly aligned.
Fix: align the buffer used.

into  mysql.com:/home/ram/work/b21476/b21476.5.1

Increase STACK_BUFF_ALLOC to avoid execution_constants test failure on the hpita2.

into  quadxeon.mysql.com:/benchmarks/ext3/TOSAVE/tsmith/bk/maint/51