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

done in previous patches.

There is an error in the Sun CC compiler that treats parameters that
differ in only qualifier as different, even though this is not
allowed by the standard (ISO/IEC 14882:2003, Section 13.1).

into  capulet.net:/home/bk/mysql-5.1-rpl

into  capulet.net:/home/bk/mysql-5.1-rpl

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

Factoring out pack_row() and unpack_row() into new files
rpl_record.{cc,h}.

Updating result files with wrong server id for BEGIN and COMMIT
events.

into  capulet.net:/home/bk/mysql-5.1-rpl

configuration with HAVE_REPLICATION undefined, which causes the
*_rows_log_event_old classes to only have a default constructor. This
generates an error on some platforms, since the base classes does 
not have a default constructor defined.

Updating signatures of do_prepare_row() for classes above, since
signatures in base classes changed.

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

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

into  mysql.com:/home/bar/mysql-5.1-new-rpl

into  mysql.com:/home/bar/mysql-5.0.b20095

Problem: single byte do_varstring1() function was called, which didn't
check limit on "number of character", and checked only "number of bytes".
Fix: adding a multi-byte aware function do_varstring1_mb(),
to limit on "number of characters"

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

- test case
- reset server id in injector

Taking code from before BUG#22583 and incorporating as events to be able
to read old events. Also incorporating old pack and unpack functions
into patch.

be skipped):

Fixing test since a replace assumed that we were on slave when we were
on master.

into  capulet.net:/home/bk/mysql-5.1-rpl

skipped):

Post-merge changes.

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

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

skipped):

By moving statement end actions from Rows_log_event::do_apply_event() to
Rows_log_event::do_update_pos() they will always be executed, even if
Rows_log_event::do_apply_event() is skipped because the event originated
at the same server. This because Rows_log_event::do_update_pos() is always
executed (unless Rows_log_event::do_apply_event() failed with an error,
in which case the slave stops with an error anyway). 

Adding test case.

Fixing logic to detect if inside a group. If a rotate event occured
when an initial prefix of events for a statement, but for which the
table did contain a key, last_event_start_time is set to zero, causing
rotate to end the group but without unlocking any tables. This left a
lock hanging around, which subsequently triggered an assertion when a
second attempt was made to lock the same sequence of tables.

In order to solve the above problem, a new flag was added to the relay
log info structure that is used to indicate that the replication thread
is currently executing a statement. Using this flag, the replication
thread is in a group if it is either in a statement or inside a trans-
action.

The patch also eliminates some gratuitous header file inclusions that
were not needed (and caused compile errors) and replaced them with
forward definitions.

into  mysql.com:/home/bar/mysql-5.1-new-rpl

  Removing wrong MYF(0) argument.

stopped at pos==4):

Submitting patch on behalf of Andrei, who discovered the problem
and provided the patch.

An update of the group relay log coordinates when rotating forgot to
update the group relay log name and only updated the group relay log
position (and group master log name and position).

This patch adds code to update the group relay log *name* as well as
the position 

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.1-merge

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.1-merge

into  mysql.com:/nfsdisk1/lars/MERGE/mysql-5.0-merge

into  mysql.com:/home/bar/mysql-5.1-new-rpl