into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  sita.local:/Users/tsmith/m/bk/maint/51

into  sin.intern.azundris.com:/home/tnurnberg/30444/51-30444

into  sin.intern.azundris.com:/home/tnurnberg/30444/50-30444

into  polly.(none):/home/kaa/src/maint/mysql-5.0-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.1-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.1-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.0-maint

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

into  polly.(none):/home/kaa/src/maint/bug5731/my51-bug5731

Issue a warning if a user sets an option or a variable to a value that is greater than a defined maximum for the option/variable.

This is for bug #29446 "Specifying a myisam_sort_buffer > 4GB on 64 bit machines not possible". Support for myisam_sort_buffer_size > 4 GB on 64-bit Windows will be looked at later in 5.2.

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

into  sin.intern.azundris.com:/home/tnurnberg/30444/51-30444

into  sin.intern.azundris.com:/home/tnurnberg/30444/50-30444

into  sin.intern.azundris.com:/home/tnurnberg/30444/51-30444

into  sin.intern.azundris.com:/home/tnurnberg/30444/50-30444

The combination of --single-transaction and --master-data requires
START TRANSACTION WITH CONSISTENT SNAPSHOT which is available from
mysqld 4.1 on. When trying this against an older server, print
diagnostic, then, if --force is not given, abort.

No test-case given since it would require a mysqld < 4.1.

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

and for bug #31070: crash during conversion of charsets

Problem: passing a 0 byte length string to some my_mb_wc_XXX() 
functions leads to server crash due to improper argument check.

Fix: properly check arguments passed to my_mb_wc_XXX() functions.

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-new-maint

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.0-maint

into  pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-new-maint

into  pilot.mysql.com:/data/msvensson/mysql/bug31167/my51-bug31167

Add --skip-innodb-adaptive-hash-index option, which is a way to
work around the bug (by disabling the adaptive hash feature entirely).

This may be useful even once the bug is fixed, for benchmarking purposes.
There are some workloads for which the adaptive hash index is not effective.

 - "on" -> "restore" to avoid warning in MSVC when compiling with debug

into  polly.(none):/home/kaa/src/maint/mysql-5.1-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.1-maint

into  polly.(none):/home/kaa/src/maint/mysql-5.0-maint

into  polly.(none):/home/kaa/src/maint/bug5731/my51-bug5731

into  polly.(none):/home/kaa/src/maint/bug5731/my50-bug5731

into  polly.(none):/home/kaa/src/maint/bug5731/my51-bug5731

into  polly.(none):/home/kaa/src/maint/bug5731/my50-bug5731

into  polly.(none):/home/kaa/src/maint/bug5731/my50-bug5731

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/51

into  ramayana.hindu.god:/home/tsmith/m/bk/maint/50

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint