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

into mysql.com:/home/mydev/mysql-5.0-5000

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

into mysql.com:/home/mydev/mysql-5.0-5000

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

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

  Fix compilation error on Windows in innobase_report_binlog_offset_and_commit()

After merge fix.

into mysql.com:/home/mydev/mysql-5.0-5000

into mysql.com:/home/psergey/mysql-5.0-bug9821

into mysql.com:/home/mydev/mysql-5.0-5000

into mysql.com:/home/psergey/mysql-5.0-bug9298-merge

into mysql.com:/home/mydev/mysql-4.1-4100

Changed the creation of the .MRG file so that only the table  name
is written when the MyISAM table is in the same database as the
MERGE table, a relative path is used in other cases in mysqld,
and possibly an absolute path is used in an embedded server.
No test case is added as the external behaviour is unchanged.
Only the file names within the .MRG file are changed.

Merge from 4.0.

This is the second of three changesets. It contains the pure bug fix.
It also contains the second after-review fixes.
The problem was that with gcc on x86, shifts are done modulo word size. 
'value' is 32 bits wide and shifting it by 32 bits is a no-op.
This was triggered by an evil distribution of character incidences. 
A distribution of 2917027827 characters made of 202 distinct values led to
34 occurrences of 32-bit Huffman codes.
This might have been the first time ever that write_bits() had to write
32-bit values. Since it can be expected that one day even 32 bits might
be insufficient, the third changeset suggests to enlarge some variables
to 64 bits.

into neptunus.(none):/home/msvensson/mysql/mysql-5.0

Setting AC_PREREQ required version to 2.50 until we have sorted out what is required. The manual says 2.58.

into neptunus.(none):/home/msvensson/mysql/mysql-5.0

value into a char field": the patch submitted for the bug a while
ago has never been reviewed or approved to push into 4.0. Decimal
support in 5.0 resolves the issue.
Adding the test case and closing the bug report.

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

into neptunus.(none):/home/msvensson/mysql/mysql-4.1

 - Remove ha_archive::rename_table and move the fix to handler::rename_table

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

Fix for avoiding gettin Invalid schema object version when doing local changes, more post review fixes

into mysql.com:/home/mydev/mysql-5.0-5000

After merge fix.

 - Different behaviuor in 5.0 pushes a warning when renaming a non existent file. Avoid that by checking that the file exists before renaming.

into neptunus.(none):/home/msvensson/mysql/mysql-4.1

Merge from 4.1

After merge fix.