into  mysql.com:/home/kent/bk/tmp/mysql-4.1-build

into  mysql.com:/home/kent/bk/tmp/mysql-4.1-build

into  mysql.com:/home/kent/bk/tmp/mysql-4.0

into  trift2.:/MySQL/M41/manpages-4.1

into  trift2.:/MySQL/M41/manpages-4.1

into  weblab.(none):/home/marcsql/TREE/mysql-4.1-runtime

into  mysql.com:/home/kent/bk/tmp/mysql-4.1-build

  EXCEPTIONS-CLIENT is now static part of repository

into  mysql.com:/home/kent/bk/tmp/mysql-4.1-build

  EXCEPTIONS-CLIENT is now static part of repository
EXCEPTIONS-CLIENT:
  BitKeeper file /home/kent/bk/tmp/mysql-4.0/EXCEPTIONS-CLIENT

into  mysql.com:/home/kent/bk/tmp/mysql-4.1-build

to the client only after the binlog write and engine commit.
No testcase for this bug, as to reproduce it, we need to "kill -9" mysqld,
which we cannot do in the testsuite. But, I tested by hand.

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-4.1-merge

into  trift2.:/MySQL/M40/mysql-4.0

The declaration of "thr_client_alarm" had got lost, keep it in "mysys/thr_alarm.c".

into  trift2.:/MySQL/M41/merge-4.1

into  kpdesk.mysql.com:/home/thek/dev/mysql-4.1-runtime

- Starting time of a query sent by file bootstrapping wasn't initialized
  and starting time defaulted to 0. This later used value by the Now-
  item and is translated to 1970-01-01 11:00:00.
- marking the time with thd->set_time() before the call to 
  mysql_parse resolves this issue.

Companion change to this one
   ChangeSet@1.2206, 2007-01-22 02:32:07+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +8 -0
     include/my_pthread.h@1.67, 2007-01-22 02:32:06+02:00, jani@a88-113-38-195.elisa-laajakaista.fi +31 -10
which renamed "sigset()" -> "my_sigset()" but forgot to do it for Windows ...

into  trift2.:/MySQL/M41/push-4.1

into  bk-internal.mysql.com:/data0/bk/mysql-4.1-opt

into  zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-maint

into  mysql.com:/home/hf/work/25492/my41-25492

Break a double declare of "uint thr_client_alarm" between "mysys/thr_alarm.c" and "mysys/my_pthread.c".

into  mysql.com:/home/tnurnberg/24660/41-24660

ENUMs weren't allowed to have character 0xff, a perfectly good character in some locales.
This was circumvented by mapping 0xff in ENUMs to ',', thereby prevent actual commas from
being used. Now if 0xff makes an appearance, we find a character not used in the enum and
use that as a separator. If no such character exists, we throw an error.

Any solution would have broken some sort of existing behaviour. This solution should
serve both fractions (those with 0xff and those with ',' in their enums), but
WILL REQUIRE A DUMP/RESTORE CYCLE FROM THOSE WITH 0xff IN THEIR ENUMS. :-/
That is, mysqldump with their current server, and restore when upgrading to one with
this patch.

into  trift2.:/MySQL/M41/push-4.1

same fix from 4.0.

into  siva.hindu.god:/home/tsmith/m/bk/maint/41

into  weblab.(none):/home/marcsql/TREE/mysql-4.1-rtmerge

into  mysql.com:/home/gluh/MySQL/Merge/4.1-opt