into  salvation.intern.azundris.com:/home/tnurnberg/21913/my41-21913

Variable character_set_results can legally be NULL (for "no conversion.")
This could result in a NULL deref that crashed the server.  Fixed.

(Although ran some additional precursory tests to see whether I could break
anything else, but no breakage so far.)

 - Dont test "encrypt" in ctype_ucs

into  shellback.(none):/home/msvensson/mysql/mysql-4.1-maint

into  rama.(none):/home/jimw/my/mysql-4.1-21288

into  zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-maint

into  zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-4.1-maint

single file is a bad practice.  

into  maint2.mysql.com:/data/localhome/tsmith/bk/41

into  maint2.mysql.com:/data/localhome/tsmith/bk/41

into  zippy.cornsilk.net:/home/cmiller/work/mysql/bug04053/my41-bug04053

	event' from master"

Since there is no repeatable test case, and this is obviously wrong, this is
the most conservative change that might possibly work.  

The syscall  read()  wasn't checked for a negative return value for an
interrupted read.  The kernel  sys_read()  returns -EINTR, and the "library" 
layer maps that to return value of -1 and sets  errno  to EINTR.  It's 
impossible (on Linux) for  read()  to set errno EINTR without the return 
value being -1 .

So, if we're checking for EINTR behavior, we should not require that the
return value be zero.

into  maint2.mysql.com:/data/localhome/tsmith/bk/bfx/41

Bug#21432 Database/Table name limited to 64 bytes, not chars, problems with multi-byte

into  maint2.mysql.com:/data/localhome/tsmith/bk/41

into  maint1.mysql.com:/data/localhome/tsmith/bk/bugfixin/41

into  moonbone.local:/work/tmp_merge-4.1-opt-mysql

into  moonbone.local:/work/tmp_merge-4.1-opt-mysql

Null merge to 5.0

Default is "var/tmp" 

into  neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint

 Must not use Item_direct_ref in HAVING because it points to
 the new value (witch is not yet calculated for the first row).

into  mysql.com:/Users/kent/mysql/bk/mysql-4.1-maint

into  maint1.mysql.com:/data/localhome/tsmith/bk/41

into  siva.hindu.god:/usr/home/tim/m/bk/41

- Fix typo in Item_func_export_set::fix_length_and_dec() which caused character set aggregation to fail
- Remove default argument from last arg of agg_arg_charsets() function, to reduce potential errors

into  siva.hindu.god:/usr/home/tim/m/bk/41

Remove some sql_print_error() calls which were triggered by user error (i.e., not server-level events at all).

Also, convert an sql_print_error -> sql_print_information for a non-error server event.

into  maint1.mysql.com:/data/localhome/tsmith/bk/41

into  lamia.home:/home/timka/mysql/src/4.1-bug-21456

GROUP BY/DISTINCT pruning optimization must be done before ORDER BY 
optimization because ORDER BY may be removed when GROUP BY/DISTINCT
sorts as a side effect, e.g. in 
  SELECT DISTINCT <non-key-col>,<pk> FROM t1
  ORDER BY <non-key-col> DISTINCT
must be removed before ORDER BY as if done the other way around
it will remove both.