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

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

  Better instructions for the user if adding of new ibdata files fails

  When calculating the buf pool dirty pages ratio, add also free pages to the LRU list length: no need to active flushing if there are lots of free pages in the buffer pool

  Search first only 10 % of the LRU list for a replaceable block before doing an LRU flush; enable again flushing of close pages also in a flush list (checkpointing) flush
trx0trx.c:
  Add forgotten return value (it was not used anywhere, fortunately)
ha_innodb.h, mysql_priv.h:
  Move declaration of srv_buf_pool_max_modified_pct to ha_innodb.h and enclose it to denote it is a C variable, not C++

  - QNX 6.2.1 actually defines HAVE_RINT
  - fixed rint(A) #define as it was causing compile errors on QNX

into the binlog), SLAVE START -> START SLAVE, error test changes.

into mysql.com:/home/mysql_src/mysql-4.1

now by default, FLUSH, OPTIMIZE, ANALYZE, REPAIR commands are written to the
binlog, unless the new NO_WRITE_TO_BINLOG keyword was used :
OPTIMIZE NO_WRITE_TO_BINLOG table t;

Previously these commands were never written to the binlog, but there are
2 reasons to change this :
- the RENAME TABLE in MERGE table bug (#175) on slave
- the possible "differently optimised queries may lead to different
updates on the master and slave" bug, until we have automatic ORDER BY.

FLUSH LOGS/SLAVE/MASTER/TABLES WITH READ LOCK are never written to the binlog.
New test for the new logging behaviour.
Other small change : reload_acl_and_cache() and reset_slave() don't send their errors themselves,
this is more usual.