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

   paths for the binary distributions (this will hopefully resolve the
   "file /usr/local/mysql/libexec/mysqld doesn't exist" error that many
   people are facing)

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

into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.for_fix

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

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

   again - even though the automake docs consider AM_CONFIG_HEADER obsolete, 
   it currently still breaks for too many people to justify this change
   at the moment.

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

Looks a bit nicer than previous one

Changed connect with timeout to use poll() instead if socket() to avoid problems with many open files

into narttu.mysql.fi:/my/mysql-4.0

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

into narttu.mysql.fi:/my/mysql-4.0

into gluh.mysql.r18.ru:/home/gluh/mysql-4.0.defweek

  In ORDER BY MySQL seems to set the key read flag also in the case where the primary key contains only a prefix of a column - not the whole column; to prevent potential bugs retrieve the whole column if the index contains a prefix of it

This way 3.23.58 slaves will always detect a 4.0.14 master (and stop)
immediately. BUG#198.

This crash happens in rather exotic case when we try to run 
SELECT DISTINCT some_func(SUM(some_field)) GROUP BY another_field;
on a table with single row.
Optimizer marks this table as const, sets group=NULL (with remove_const)
thus, create_tmp_table makes mistake collecting columns for temporary table
and then crashes because the field_count gets less than hidden_columns_count.

So now for the CREATE TABLE foo (id integer NOT NULL default 9)
INSERT INTO foo VALUES (NULL); we get an error
INSERT INTO foo VALUES (1), (NULL), (2); we get one warning
          and second record is set to 9

Is that what we want?

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

Safe parenthesis.

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

   problem on Windows/cygwin (BUG#668)

Task ID 894:
Backport default_week_format variable to 4.0

  Track an assertion failure reported on the mailing list June 18th, 2003

 - fixed a typo

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