into  debian.(none):/M51/push-5.1

into  debian.(none):/M51/bug14685-5.1

                        in a build "--without-server".

Fix for bug#14685

into  debian.(none):/M51/push-5.1

into  blade09.mysql.com:/tmp/mmj/mysql-5.1-runtime

into  mysql.com:/d2/hf/mrg/mysql-5.1-opt

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

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

into  weblab.(none):/home/marcsql/TREE/mysql-5.1-rt-merge

into  moonbone.local:/mnt/gentoo64/work/bk-trees/mysql-5.1-opt

into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1

into  gshchepa.loc:/home/uchum/work/bk-trees/mysql-5.0-opt-27704

into  gshchepa.loc:/home/uchum/work/bk-trees/mysql-5.0-opt-27704

into  debian.(none):/M51/push-5.1

Support for NULL components was incomplete for row comparison,
fixed.  Added support for abort_on_null at compare_row() like
in 5.x

into  debian.(none):/M51/push-5.1

into  debian.(none):/M51/bug27739-5.1

into  magare.gmz:/home/kgeorge/mysql/autopush/B27786-5.0-opt

This bug was intruduced by the fix for bug#17212 (in 4.1). It is not 
ok to call test_if_skip_sort_order since this function will 
alter the execution plan. By contract it is not ok to call 
test_if_skip_sort_order in this context.

This bug appears only in the case when the optimizer has chosen 
an index for accessing a particular table but finds a covering 
index that enables it to skip ORDER BY. This happens in 
test_if_skip_sort_order.

into  romeo.(none):/home/bk/merge-mysql-5.1

                 not some other tool (file system checker on Tru64).

Patch originally supplied by Peter O'Gorman, slightly modified by me.

Bug#27739 "build fails on Tru64 due to icheck test in configure"

into  romeo.(none):/home/bk/merge-mysql-5.1

into  romeo.(none):/home/bk/merge-mysql-5.0

into  romeo.(none):/home/bkroot/mysql-5.0-rpl

into  romeo.(none):/home/bk/b27779-mysql-5.1-rpl

When merging views into the enclosing statement
the ORDER BY clause of the view is merged to the
parent's ORDER BY clause.
However when the VIEW is merged into an UNION
branch the ORDER BY should be ignored. 
Use of ORDER BY for individual SELECT statements
implies nothing about the order in which the rows
appear in the final result because UNION by default
produces unordered set of rows.
Fixed by ignoring the ORDER BY clause from the merge
view when expanded in an UNION branch.

into  magare.gmz:/home/kgeorge/mysql/autopush/B27530-5.0-opt

They can drop table after table names list creation and before table opening.
We open non existing table and get ER_NO_SUCH_TABLE error.
In this case we do not store the record into I_S table and clear error.

revert back to old show_binlog_events asto many test failures, and create a show_binlog_events2 instead

 - test case

into  debian.(none):/M50/push-5.0

into  trift2.:/MySQL/M50/push-5.0