into  maint2.mysql.com:/data/localhome/tsmith/bk/51

into  maint2.mysql.com:/data/localhome/tsmith/bk/bfx/51

into  maint2.mysql.com:/data/localhome/tsmith/bk/bfx/50

into  maint2.mysql.com:/data/localhome/tsmith/bk/bfx/41

into  neptunus.(none):/home/msvensson/mysql/bug21813/my51-bug21813

 - Use the "%.*b" format when printing prepared and exeuted prepared statements to the log.
 - Add test case to check that also prepared statements end up in the query log
Bug#14346 Prepared statements corrupting general log/server memory
 - Use "stmt->query" when logging the newly prepared query instead of "packet"

into  gbichot3.local:/home/mysql_src/mysql-5.1-maint

into  polly.local:/home/kaa/src/maint/m51-new-maint--07OGx

into  polly.local:/home/kaa/src/maint/m50-maint--07OGt

into  gbichot3.local:/home/mysql_src/mysql-5.1-maint

and its duplicate BUG#19057 "Test 'rpl_row_func003' fails on SuSE SLES9 x86".
It was an assertion failure, only in debug builds, not present
in released versions (nothing to document).
It happened when doing SHOW TABLE STATUS on an InnoDB table
having an auto_increment column, right after creating the table.
The test which would have caught this problem was disabled in 
mid-April for another reason (how much I like tests disabled for
months...).

into  rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-5.1-new-maint_21527

    
init_dumping now accepts a function pointer to the table or view specific init_dumping function.  This allows both tables and views to use the init_dumping function.

into  salvation.intern.azundris.com:/home/tnurnberg/mysql-5.1-maint

into  salvation.intern.azundris.com:/home/tnurnberg/mysql-5.1

into  zim.(none):/home/brian/mysql/arch-5.1

into  zim.(none):/home/brian/mysql/arch-5.1

Fixed "discover" in the handler API.

Fixed problem where handlerton was not zero'ed. I need to look around, I suspect this problem is more widespread. 

into  zippy.cornsilk.net:/home/cmiller/work/mysql/release/mysql-5.0-maint

	InterfaceError on connect

Removed the bool flag from the st_mysql_options struct, since it adds 
another word in size to the memory size and shifts member memory locations
down, both of which break binary-interface compatibility.

Instead, use a flag, 2**30, in the client_options bit-field to represent
that the client should check the SSL certificate of the server.

Fixed stacktrace dumps for i386/NPTL

into  zippy.cornsilk.net:/home/cmiller/work/mysql/merge/mysql-5.1-new-maint

into  salvation.intern.azundris.com:/home/tnurnberg/mysql-5.1-maint

into  rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-5.1-new-maint_11972

into  salvation.intern.azundris.com:/home/tnurnberg/mysql-5.1-maint

into  rolltop.ignatz42.dyndns.org:/mnt/storeage/mysql-5.0-maint_11972

The mysql client uses the default character set on reconnect.  The default character set is now controled by the client charset command while the client is running.  The charset command now also issues a SET NAMES command to the server to make sure that the client's charset settings are in sync with the server's.

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

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

into  mysql.com:/Users/kent/mysql/bk/mysql-5.1-maint

into  mysql.com:/Users/kent/mysql/bk/mysql-5.1-maint

into  neptunus.(none):/home/msvensson/mysql/mysql-5.1-new-maint