Character set is not displayed in "Type" column anymore
In "Collation" column NULL instead of BINARY is now displayd for for non-character data types

into bar.mysql.r18.ru:/usr/home/bar/mysql-4.1

Collation and coercibility tests for string functions

into light.hegel.local:C:/mysql-dev/mysql-4.1

USER(), DATABASE() and VERSION() return in utf8 now

This is because rpl_relayrotate.test uses InnoDB.
Example of a failing sequence:
rpl_relayrotate.test repl_user_variables.test rpl_relayrotate.test
Explaination in the files.
Btw all other tests which use InnoDB (innodb*.test) already have this final
DROP TABLE.
Removed a wrong comment of mine.

  default_collation is now displayed correctly in mysqld --help
  mysqld --help now displays default_collation corretly, according to --default-character-set

Fixed that SHOW CHARACTER SET displayed non-dynamic charsets even if they were not really compiled

  Typos fixes

  Bug fix: latin1 is not compiled charset and is not specified..
mysql.cc:
  Bug fix: latin1 is not compiled charset and is not specified...

Added initialization of all important global variables

collation_client  -> character_set_client
collation_results -> character_set_results
character_set     -> character_set_server

SET NAMES now doesn't start client->server conversion
SET CHARACTER SET now starts both client->server and server->client conversion

into bar.mysql.r18.ru:/usr/home/bar/mysql-4.1

 "character_set_system" has been added to display the system character set

into bar.mysql.r18.ru:/usr/home/bar/mysql-4.1

into myvenu.com:/home/venu/work/sql/dev-4.1

  Updated protocol test

into mysql.r18.ru:/usr/home/ram/work/mysql-4.1.latest

--default-character-set and --default-collation 

Added MYSQL_TYPE_NULL as a dummy bind case for fetch buffers
Fix for offset based re-fetch using mysql_fetch_column
Misc cleanups for ODBC compatibility

into eagle.mysql.r18.ru:/home/vva/work/LOADDATA/mysql-4.1

version is '-log', '-debug' etc.

into narttu.mysql.fi:/my/mysql-4.0