Do not issue a 'read-only' error in case of DROP TEMPORARY TABLE on a non-existing temporary table.
Instead produce the correct "Unknown table" error or warning (in cases when the IF EXISTS clause was specified).

To a documentor: the part of the manual describing the 'read_only' system variable should be clarified to state the following:
"When the read_only variable is set to ON, all operations which create/update/drop tables are rejected with the exceptions for:
1. Any operation performed by the replication thread on a slave server
2. Any operation performed by a user that have the SUPER privilege
3. Any operation that creates/updates/drops only temporary tables"

The code that set up data to be passed to user-defined functions was very
old and analyzed the "Type" of the data that was passed into the UDF, when
it really should analyze the "return_type", which is hard-coded for simple
Items and works correctly for complex ones like functions.
---
Added test at Sergei's behest.

It's not possible to flush the global status variables in 5.0
Update test case so it works by recording the value of handle_rollback
before and compare it to the value after

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

into  mysql.com:/usr/home/ram/work/bug22158/my50-bug22158

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

 - Improve icheck rules in Makefile.am

 - Add two null bytes in  "buff" variable allowing us to call
   get_arg two times also for strings longer than sizeof(buff) 

When executing the init_connect statement, thd->net.vio is set to 0, to         
forbid sending any results to the client. As a side effect we don't log         
possible errors, either.                                                        
                                                                                
Now we write warnings to the error log if an init_connect query                
fails.                                                                          

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

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

Remove one warning

Disable warnings around the create table statements, we want to use innodb when possible but they work just fine without.

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

Update the binlog format parse routine to only be avaliable in 5.1 and allow for any binlog_format to be specified

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

Fix two memory leaks in mysql_client_test

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

Add comments
Deperlify

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

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

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

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

BUG#23427 incompatible ABI change in 5.0.26?
   - Use the icheck tool if avaliable and compare the current mysql.h to a version
controlled reference file 

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

 - Fix check in mysql_client_test to reflect the change of datatype
   for DEFAULT column

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

Flush both stdout and stderr before abort'ing mysql_client_test

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

with error 1 and we are running with --force
The specific "analyze" code is enclosed in a .test file fwich can easily
be modified to be more advanced 

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

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