into serg.mylan:/usr/home/serg/Abk/mysql-4.1

into ltantony.rdg.cyberkinetica.homeunix.net:/usr/home/antony/work/wl638.3

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

  Rework parser expression rules
  Rework handling for "||" concat/or
  Eliminate some shift/reduce conflicts
  Add support for "xxx IS [ NOT ] truth_value"

into gluh.mysql.r18.ru:/home/gluh/MySQL/mysql-5.0.1

code cleanup

Moving the part of user_var.test using UCS2 to ctype_ucs.test

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

AC_FUNC_MMAP changes to AC_CHECK_FUNCS(mmap)

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

into rurik.mysql.com:/home/igor/mysql-4.1

into mysql.com:/dbdata/psergey/mysql-4.1-heap-bug

into rurik.mysql.com:/home/igor/dev/mysql-4.1-0

  Added a test case for bug #6447.
mf_keycache.c:
  Fixed bug #6447. Erronious code in the key_cache_read function
  caused problems when reading key blocks with offset>0 into
  key cache. The code of key_cache_insert and key_cache_write
  was modified similarly.

into hundin.mysql.fi:/home/heikki/mysql-4.1

  Anthony's http://lists.mysql.com/internals/18505 patch for DROP DATABASE broke caused it to return errno if .ibd files were present (bas_ext() was obsolete in ha_innodb.cc); fix this

Manually ported this bug fix from 4.0: 
 Fix InnoDB bug #6287: if one uses INSERT IGNORE to insert several rows at a time, and the first inserts are ignored because of a duplicate key collision, then InnoDB in a replication slave assigns AUTO_INCREMENT values 1 bigger than in the master

  Fix InnoDB bug #6287: if one uses INSERT IGNORE to insert several rows at a time, and the first inserts are ignored because of a duplicate key collision, then InnoDB in a replication slave assigns AUTO_INCREMENT values 1 bigger than in the master

into mysql.com:/dbdata/psergey/mysql-4.1-heap-bug

into sinisa.nasamreza.org:/mnt/work/petica

into sinisa.nasamreza.org:/mnt/work/petica

unresolved symbols.

  reverting previous patch

into mysql.com:/usr/home/bar/mysql-4.1

  Space allocated didn't take in account trailing '\0' bytes.

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

Also print warning if there is an ndb->mysql errorcode mapping, this since the warning provides valuable info to the user