aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorlmadsen <lmadsen@f38db490-d61c-443f-a65b-d21fe96a405b>2010-04-15 13:41:45 +0000
committerlmadsen <lmadsen@f38db490-d61c-443f-a65b-d21fe96a405b>2010-04-15 13:41:45 +0000
commitd4412bb43f83c62b0470c699729063efbec3fa04 (patch)
tree1684193ce7298f12ceab7ac3ff8a0c62a85a056c
parent69bd512b1a41b4aab13f9522527a3d9b41ce3f4c (diff)
Update address of the bug tracker.
git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.4@257342 f38db490-d61c-443f-a65b-d21fe96a405b
-rw-r--r--doc/backtrace.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/backtrace.txt b/doc/backtrace.txt
index ce39b0a3e..ed3b5bb7b 100644
--- a/doc/backtrace.txt
+++ b/doc/backtrace.txt
@@ -1,6 +1,8 @@
This document is intended to provide information on how to obtain the
backtraces required on the asterisk bug tracker, available at
-http://bugs.digium.com. The information is required by developers to
+http://issues.asterisk.org.
+
+The information is required by developers to
help fix problem with bugs of any kind. Backtraces provide information
about what was wrong when a program crashed; in our case,
Asterisk. There are two kind of backtraces (aka 'bt') which are