bk commit into 5.1 tree (iggy:1.2331)

[Ignacio Galarza]

Below is the list of changes that have just been committed into a local
5.1 repository of iggy. When iggy does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet@stripped, 2006-09-28 14:01:12-04:00, iggy@stripped +1 -0
  Merge rolltop.ignatz42.dyndns.org:/mnt/storeage/bug21449/my50-bug21449
  into  rolltop.ignatz42.dyndns.org:/mnt/storeage/bug21449/my51-bug21449
  MERGE: 1.1810.1697.166

  sql/stacktrace.c@stripped, 2006-09-28 14:00:51-04:00, iggy@stripped +0 -0
    Auto merged
    MERGE: 1.18.1.3

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	iggy
# Host:	rolltop.ignatz42.dyndns.org
# Root:	/mnt/storeage/bug21449/my51-bug21449/RESYNC

--- 1.21/sql/stacktrace.c	2006-09-28 14:01:45 -04:00
+++ 1.22/sql/stacktrace.c	2006-09-28 14:01:45 -04:00
@@ -222,7 +222,7 @@
   fprintf(stderr, "Stack trace seems successful - bottom reached\n");
 
 end:
-  fprintf(stderr, "Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved\n\
+  fprintf(stderr, "Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved\n\
 stack trace is much more helpful in diagnosing the problem, so please do \n\
 resolve it\n");
 }