Stop the line wrapping for warnings.
  it needs for warnings statistic in code coverage

Make mysqlbinlog prompt for the password if
mysqlbinlog -p
instead of printing the usage().
This makes mysqlbinlog behave like other clients, which is the reason
why we fix this in 3.23.
This new code was almost copied from mysqldump.
Note that before, one could use
mysqlbinlog -p pass
and now one must use
mysqlbinlog -ppass
(putting a space will ask for the password).

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

into mishka.mysql.fi:/home/my/mysql-3.23

into eagle.mysql.r18.ru:/home/vva/work/BUG_1378/mysql-3.23

The 4.0 changeset was:
ChangeSet@1.1579.3.1, 2003-09-26 23:43:22+02:00, guilhem@mysql.com
  Fix for 64-bit machines.
  I am almost sure this is the cause for
  BUG#1381 [Opn]: Bug in replication on HP-UX 64 bit binaries?
  BUG#1256 [CRp]: Replication slave fails to connect to master in 64-bit version
 (Solaris)
  The reason why I think it's wrong is that the normal client code has
  uint32 ip_addr.
  (of course on 32-bit machines it does not matter, but on 64-bit it does).

 - Tagged ChangeSet 1.1413 as "mysql-3.23.58"

DO NOT COPY THIS CODE TO 4.0. The bugfix is better in 4.0,
but here in 3.23 we don't want to add a new error code so
we just use ER_EMPTY_QUERY. Bug was:
"If a query was ignored on the slave (because of
@code{replicate-ignore-table} and other similar rules), the slave
still checked if the query got the same error code (0, no error) as on
the master. So if the master had an error on the query (for example,
``Duplicate entry'' in a multiple-row insert), then the slave stopped
and warned that the error codes didn't match. (Bug #797)"

   to be able to compile on HP-UX 10.20 (which does not have in_add_t).

proper obligatory quoting of identifiers in mysqldump<->server communication (unrelated from command-line options)

into narttu.mysql.fi:/my/mysql-3.23

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

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

That's to make resolveip work on our FreeBSD-5.0/Sparc64 build host.

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

the bug with 3.23.
ChangeSet@1.1416.113.1, 2003-03-22 15:22:59+01:00, guilhem@mysql.com
  Fix for #178  Replicating INSERT VALUES(USER()) crashes (SEGV) the slave
      Now it does not SEGV, but USER() is still badly replicated
      (it is replicated to ""), which is a lower priority bug.

  Backport from 4.0 of the btr0sea.c latch hang fix

into mashka.mysql.fi:/home/my/mysql-3.23

was used with NULL value on NOT NULL column. (Bug #479)

into eagle.mysql.r18.ru:/home/vva/work/BUG_479_/mysql-3.23

repository (incredible that I forgot to push, but why not).
So unfortunately the bugfix missed 3.23.57 and will be in .58 :(
Instead of looking like working (bug #198), replication between
a 3.23 slave and 4.0 master should frankly stop. Here we detect
4.0 masters in the 3.23 slave code when we see a strange Rotate
event, and in that case we print an error and stop.
4.0.13 and older masters will be "often" caught (see the patch); 4.0.14
and newer masters will always be immediately caught.