Fixed wrong number of warnings/duplicates for machines with high-byte-first

into mishka.local:/home/my/mysql-4.1

New records_in_range() interface (similar to read_range())
Macros for faster bitmap handling
Simplify read_range() code (#WL1786)
New general key_cmp() function to compare keys

into mysql.com:/home/my/mysql-4.1

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

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

by adding sleep-and-retries (max 4 times) if MASTER_POS_WAIT() returns NULL
in sync_with_master and sync_slave_with_master.
The problem showed up only today, in MySQL 5.0 in rpl_server_id2.test,
but may affect 4.x as well, so fixing it here. Note that I am also fixing
5.0 too, with the same exact patch, because I don't want to leave 5.0 broken
until the next 4.0->4.1->5.0 merge.

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

  Fix remaining cases of Bug #3596: fix possible races caused by an obsolete value of thd->query_length in SHOW PROCESSLIST and SHOW INNODB STATUS; this fix depends on the fact that thd->query is always set to NULL before setting it to point to a new query

into hundin.mysql.fi:/home/marko/j/mysql-4.1

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

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

This change fixes SHOW GRANTS problem, while EXPLAIN will be fixed
in a separate patch.

  Fix bug #3749: if there were several indexs that made an automatically generated FOREIGN KEY index redundant, then MySQL miscalculated the number of keys, and the AUTO_INCREMENT flag was forgotten by MySQL from a PRIMARY KEY. There were probably a multitude of other errors caused by this.

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

Reserve the MySQL LOCK_thread_count mutex when printing thd->query of
an arbitrary transaction; if we are printing thd->query of a transaction that
we know is currently executing inside InnoDB, then we know that MySQL cannot
meanwhile change thd->query, and no need to reserve the MySQL mutex; note
that this patch still leaves open the possibility of races in MySQL's
thd->query_len

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

  A flawed fix of the thd->query race in SHOW INNODB STATUS; see the comments in code about how to fix this properly; we cannot use LOCK_thread_count to protect thd->query, because that will cause a deadlock of threads

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

   make_binary_distribution (bug#2857)