Merged revisions 257343 via svnmerge from

https://origsvn.digium.com/svn/asterisk/trunk

................
  r257343 | lmadsen | 2010-04-15 08:44:38 -0500 (Thu, 15 Apr 2010) | 9 lines

  Merged revisions 257342 via svnmerge from
  https://origsvn.digium.com/svn/asterisk/branches/1.4

  ........
    r257342 | lmadsen | 2010-04-15 08:41:45 -0500 (Thu, 15 Apr 2010) | 1 line

    Update address of the bug tracker.
  ........
................

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.6.1@257345 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/doc/backtrace.txt b/doc/backtrace.txt
index caf1579ce4ef5aa0b5f0eb372ee223b0c7edd00c..4572e24575a0e391822facc83663ed4023645c54 100644 (file)
--- 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