into mysql.com:/my/mysql-4.1

  On 64-bit Windows use InnoDB's own printf function where %lu is converted to %I64u; this eliminates Intel compiler warnings on IA64

All tests pass (client_test included)

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

"USE db"  affected the character set of further CREATE DATABASEs,
which should have not happened.

Cleaned up embedded library access and query cache handling
Changed min stack size to 128K (to allow longer MyISAM keys)
Fixed wrong priority for XOR (should be less than NEG to get -1^1 to work)

into mysql.com:/space/my/mysql-4.1

platforms.

into deer.(none):/home/hf/work/mysql-4.1.2126

additional changes (after discussion with Monty)

Fixed not updated test from last changeset

now mysql_server_init is called from mysql_init with fake parameters
mysql_once_init code included to mysql_server_init.
embedded-specific initialization is in init_embedded_server function

into mysql.com:/my/mysql-4.0

New Statement: SHOW [STORAGE] ENGINES
New System Variable: storage_engine
New mysqld Argument: --default-storage-engine=

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

release the mutex before exiting the function, or it will be kept forever
(=> START SLAVE, STOP SLAVE, etc will hang).

into eagle.mysql.r18.ru:/home/vva/work/BUG_2023/mysql-4.0

(char * -> const char*)

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

more general message when slave can't start because of incorrect
replication information, the previous one was sometimes a misleading
indication (i.e. sometimes the problem had nothing to do with
system permissions).
The perfect fix would be to report the exact error to the client
(instead of pointing the client to the error log); this is a bit
of work so it's more a development task:
WL#1088 "Move all hardcoded messages of replication to share/errmsg.txt".
I was not able to modify the errmsg.txt in these sql/ subdirectories:

danish
dutch
german
italian
portuguese
russian
spanish
swedish
ukrainian

   tagged/released
 - tagged ChangeSet@1.1655.1.3 as mysql-4.0.17

into rhols221.adsl.netsonic.fi:/home/my/bk/mysql-4.1

   a missing space)
 - Define the subject of the failure mail reports within the calling script
   instead of logger.pm

note: bar asked me to use res.charset in ::sql_type() functions to be more consistent.

into sinisa.nasamreza.org:/mnt/work/mysql-4.0

in decimal type with prepended zero's.