let's not assume that char is signed (its signedness is not defined).
The server was also affected by the wrong typedef.

 Fix for Bug#6025 "Test "client_test" fails in 4.1.6-gamma build (2)".
 No need for a test case, the bug is covered already.

  Fix a typo. Cleanup.

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

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

into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1

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

   mysqlclient.dsp project files

into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1

  Wrong handler.

  Bug#6086 "ctype_utf8" test fails when MySQL does not include InnoDB support

into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1

into mysql.com:/media/sda1/mysql/mysql-4.1-5985

crashes server." The fix makes Item_func_rand prepared-statements
aware plus it fixes the case when RAND is used in prepared
statements and replication is on (as well as several similar issues).
Until now we did not reset THD before every execution of a prepared
statement, so if some execution had set thd->time_zone_used
or thd->rand_used they would not be reset until next mysql_parse.
Some of post-review fixes done.

into sanja.is.com.ua:/home/bell/mysql/bk/work-4.1

  Implement innobase_very_fast_shutdown and innobase_start_trx_and_assign_read_view(); these were requested by Guilhem

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

BUG#4335 - one name can be handler open'ed many times.
Fixed problems detected on Windows build by VC++.
Removed unused variables.
Applied a neccessary cast.

  Make checks (asserts) performed in client_test.c work in non-debug
  builds.

(bad merge from 4.0)

  Added catch for (example) WL#1234 into bk commit subjects

propogation works only once (prepared statements)".

- 'ps_10nestset' uses a "nested set" approach for an employee 
  hierarchy, then does arithmetic on the "salary" field;
  (soon) to be extended by inserts / deletes which imply
  mass updates on the "l"/"r" fields showing the set inclusion,
- 'ps_11bugs' will get (some of ?) those bug DB entries which
  refer to prepared statements, but whose number does not appear
  in a test file comment - so it will also be extended.

  A fix for Bug#6042 "constants propogation works olny once (prepared
  statements)": reset item->marker in Item::cleanup, as it's used
  in propogate_cond_constants. No test case as the only way I could
  come up with to show the problem is EXPLAIN, and EXPLAIN is painful
  to use in the test suite.

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1

into a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-4.1

section, which had gotten somewhat out-dated.

into gw.mysql.r18.ru:/usr/home/ram/work/4.1.b5382

into poseidon.ndb.mysql.com:/home/tomas/mysql-4.1