into  sin.intern.azundris.com:/home/tnurnberg/22540/50-22540

previous correction didn't. make sure "tail" is fixed up
when filling cache several times; rework formulae.

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint

 - Use SQL for diffing master and slave

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint

 - Move the check of too long path to 'get_one_option'

into  damien-katzs-computer.local:/Users/dkatz/mysql50

show that shm communication still works on windows,
and that we can't overflow the base-name.

Windows fixies

into  sin.intern.azundris.com:/home/tnurnberg/22540/50-22540

windows fixies

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint

into  pilot.(none):/data/msvensson/mysql/mysql-5.0-maint

into  sin.intern.azundris.com:/home/tnurnberg/22540/50-22540

into  damien-katzs-computer.local:/Users/dkatz/50

Added more sleep time befoe reap to allow query to be executed.

into  maint1.mysql.com:/data/localhome/tsmith/bk/maint/50

into  amd64.(none):/src/bug24732/my50-bug24732

- Corrected manifest attributes.

 - Various fixes for running mysql-test-run.pl on ActiveState perl
   for windows. Reading it's source in win32/win32.c helps...

into  pilot.(none):/data/msvensson/mysql/bug25657/my50-bug25657-new2

end_log_pos data within a transaction are relative to
the start of the transaction rather than absolute.
we fix those groups in situ before writing the log out.

additional comments and handling for groups with very
large single events, as suggested by Guilhem.

fix binlog-writing so that end_log_pos is given correctly even
within transactions for both SHOW BINLOG and SHOW MASTER STATUS,
that is as absolute values (from log start) rather than relative
values (from transaction's start).
---
Merge tnurnberg@bk-internal.mysql.com:/home/bk/mysql-5.0-maint
into  sin.intern.azundris.com:/home/tnurnberg/22540/50-22540

into  gleb.loc:/home/uchum/work/bk/5.0-opt

into  gleb.loc:/home/uchum/work/bk/5.0-opt

into  gleb.loc:/home/uchum/work/bk/4.1-opt

into  olga.mysql.com:/home/igor/dev-opt/mysql-5.0-opt-bug25602

into  gleb.loc:/home/uchum/work/bk/5.0-opt

the loose scan optimization for grouping queries was applied returned 
a wrong result set when the query was used with the SQL_BIG_RESULT
option.

The SQL_BIG_RESULT option forces to use sorting algorithm for grouping
queries instead of employing a suitable index. The current loose scan
optimization is applied only for one table queries when the suitable
index is covering. It does not make sense to use sort algorithm in this
case. However the create_sort_index function does not take into account
the possible choice of the loose scan to implement the DISTINCT operator
which makes sorting unnecessary. Moreover the current implementation of
the loose scan for queries with distinct assumes that sorting will
never happen. Thus in this case create_sort_index should not call
the function filesort.

into  gleb.loc:/home/uchum/work/bk/5.0-opt

into  gleb.loc:/home/uchum/work/bk/5.0-opt

INSERT into table from SELECT from the same table
with ORDER BY and LIMIT was inserting other data
than sole SELECT ... ORDER BY ... LIMIT returns.

One part of the patch for bug #9676 improperly pushed
LIMIT to temporary table in the presence of the ORDER BY
clause.
That part has been removed.

into  mysql.com:/home/ram/work/b29079/b29079.5.0

into  mysql.com:/home/ram/work/b29079/b29079.5.0

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

to be run only if it is available on the machine.

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