Fix bug #5414 in 4.1: srv_max_n_threads was always set to only 1000, regardless of the buffer pool size; undelr very high concurrent loads this could cause an assertion failure in sync0arr.c line 384 when we ran out of wait slots for threads; also innodb_thread_concurrency did not work, because the wait queue also there overflowed at 1000 concurrent threads; also remove redundant code
trx0undo.c:
  Add a missing newline to fprints

into gluh.mysql.r18.ru:/home/gluh/MySQL-BUGS/mysql-4.1

server': the bug occurs when arguments of LIKE function are in 
differentcharacter sets. If these character sets are compatible, 
we create an item-converter. In prepared mode, this item
needs to be created in memory of current prepared statement.

  Allow FROM or IN in SHOW KEYS, as in other SHOW statements.

mysql_create_system_tables, just in case

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

2. changed key_* to el_ley_* in the libedit key.h
   (because it's in the conflict with the aix definitions)
3. use libedit_term.h instead of term.h in the cmd-line-utils/libedit/el.h
4. added definition of MIN in the cmd-line-utils/libedit/read.c 
   (if it wasn't defined yet)
5. discarded definition of SUNOS macro from configure.in 
   (now we don't include term.h in the el.h at all)

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

Add missing parameter to strxnmov() that caused some INTO OUTFILE commands to core dump

  Add GPL comment

into mysql.com:/Users/mikron/mysql-4.1

  Change a reference to ibman.php to a reference in the MySQL manual; someone should change the 20 other places in the source code where we still refer to ibman.php

parameters": when unpacking binary time recieved from client, handle
the case when length is 0: it means all MYSQL_TIME members are zero.

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

than 32 bytes. getWords interpreted length as number of words and
got number of bytes.

into mysql.com:/Users/mikron/mysql-4.1

into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b5232

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

into hundin.mysql.fi:/home/marko/k/mysql-4.1

into hundin.mysql.fi:/home/marko/k/mysql-4.1

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

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

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

  If ALTER TABLE ... DROP FOREIGN KEY ... fails because of a wrong constraint name, return a table handler error number 150 instead of 152; the value 152 was misleading, as it referred to '152 = Cannot delete a parent row', whereas '150 = Foreign key constraint is incorrectly formed' is less misleading

  row_drop_table_for_mysql(): Removed duplicated block of code.