The problem yesterday in ERROR_LOCK_VIOLATION was not InnoDB Hot Backup, but some file system backup tool: add to file writes 100 retries with 1 second waits

  Backport from 4.0: convert TL_READ_NO_INSERT to TL_READ to allow concurrent inserts to the table in INSERT INTO ... SELECT ... FROM table

  Fix an assertion about ERROR_LOCK_VIOLATION 33 in file write if InnoDB Hot Backup is run concurrently with mysqld in Windows

This fixes a possible core dump problem in SHOW PROCESSLIST

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

  Backport from 4.0: fix bug in adaptive hash index search

(like FLUSH TABLES).
(Code is already in 4.0)

  Backport from 4.0: fix the BLOB hang if the index tree is of height 1

  Backport from 4.0: fix possible adaprive hash index latch hang

  Backport bugfix from 4.0: combined log file size >= 2 GB could cause log to be written in wrong place
btr0pcur.c:
  Backport bugfix from 4.0: index cursor restoration could theoretically fail

(To make the current tests results work on windows)

This fixed a bug in GROUP BY on a BLOB column with NULL values.

   (There are probably some more to fix)

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

Safety fix to not cause conflicts with extended packages in 4.0.

   for the Debian project) to fix some architecture-specific problems
   and some bugs

  Remove an assertion which can fail in a race of 3 threads

into sergbook.mysql.com:/usr/home/serg/Abk/mysql

  Better error message to help users who created tables with < 3.23.54 where MySQL implicitly added a PRIMARY KEY definition

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

database and lower case table names.

This fixes a bug with REPAIR TABLE t1 USE_FRM on windows.

tables.  This removes a possible deadlock situation.

   spotting and reporting this)

 - bumped up version number in configure.in to 3.23.55