into eagle.mysql.r18.ru:/home/vva/work/BUG_1851/mysql-4.1

an error code if the output device is filled"

into sanja.is.com.ua:/home/bell/mysql/bk/mysql-4.1

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

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

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

   build thread

into sanja.is.com.ua:/home/bell/mysql/bk/work-innodb-4.1

into sanja.is.com.ua:/home/bell/mysql/bk/work-innodb-4.1

   project file

result of SHOW TABLE STATUS

into sanja.is.com.ua:/home/bell/mysql/bk/work-innodb-4.1

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

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

work (prepared statements)" and after-review fixes:
- str_to_TIME renamed to str_to_datetime to pair with str_to_time
- functions str_to_time and str_to_TIME moved to sql-common
- send_data_str now supports MYSQL_TYPE_TIME, MYSQL_TIME_DATE,
  MYSQL_TIME_DATETIME types of user input buffers.
- few more comments in the client library
- a test case added.

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

into mysql.com:/usr/local/home/marty/MySQL/test/mysql-4.1

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

into poseidon.bredbandsbolaget.se:/home/tomas/mysql-4.1-clean

you just need to change this line of mysqld.cc:
#if MYSQL_VERSION_ID >= 40103
to, say,
#if MYSQL_VERSION_ID > 40103
I am noticing a failure of bdb.test; I believe this is not related to the
code I added yesterday and today, but I am checking. In any case I push this
changeset as it cannot by itself bring more mess that I *may* (or not)
already have brought with previous pushes.

into mysql.com:/dbdata/psergey/mysql-4.1-root

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

into mysql.com:/home/jonas/src/mysql-4.1

   file and sql/tztime.cpp to the libmysqld project file

(the previous commit was in "non" fresh clone :-()

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

a limitation of yesterday's implementation:
if there was an unfinished transaction (COMMIT not typed), and some MyISAM tables were
then updated, and then mysqld crashes, then at restart the server would use the too old
binlog offset known by InnoDB to cut the binlog, thus cutting the successful MyISAM
updates. We fix this by reporting the binlog offset into InnoDB even if InnoDB was not
affected at all by the update.
But the feature is still disabled until we decide if it can go into 4.1.3.

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

into sanja.is.com.ua:/home/bell/mysql/bk/work-innodb-4.1