into mysql.com:/bk/mysql-4.1

 - tagged ChangeSet 1.1641 as "mysql-4.1.1"

  minor edits

into ice.snake.net:/Volumes/ice2/MySQL/bk/mysql-4.1

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

into mysql.com:/home/kostja/mysql/mysql-4.1-root

Second edition: error message was deleted as Segey suggested
Now name of the constraint will be used as the name of the key
if the last not specified

   added to manual.texi - extract it from there instead.

thd->command can be anything except COM_EXECUTE in no cases
except programming error.

Ensure that innodb is created for the first replication test as the slave-timeout is lower for future tests and this failed on some slower machines

into mysql.com:/home/kostja/mysql/mysql-4.1-root

  Fixed inconsistency of values of used_tables_cache and
  const_item_cache for Item_func_isnull objects (bug #1990).

followup of Bordeaux Optimizer session

into mysql.com:/home/kostja/mysql/mysql-4.1-root

all items in free_prep_stmt(free_items);

indentation fix

Added --protocol to mysqlbinlog

into mysql.com:/my/mysql-4.1

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

It happens that mysql->client_next->client_next=mysql
and mysql_close() goes into infinite loop.
Results vary from simple sigsegv (FreeBSD), to hard system lockup (Linux)
:)

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

the relay log before flushing master.info.
Doing 'before' leads to duplicate event, doing after leads to missing event.
Both can be as destructive, but 'duplicate' enables us to later add detection
code to catch it. Whereas 'missing' can't be caught (it can't, because
the I/O thread can produce legal position jumps, for example if it has
ignored an event coming from this slave (rememember that starting from 4.1.1,
the I/O thread filters the server id). 

into mysql.com:/home/kostja/mysql/mysql-4.1-root

into mysql.com:/my/mysql-4.0

into mysql.com:/my/mysql-4.1

into mysql.com:/my/mysql-4.1

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

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