kenmirrors/asterisk
1
0
Fork 0
mirror of https://github.com/asterisk/asterisk.git synced 2025-10-31 02:37:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update references to bugs.digium.com and reviewboard.digium.com to the new URLs.

Browse Source 
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@197824 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Sean Bright
2009-05-28 21:50:27 +00:00
parent 0941c2c32e
commit f51bb019bb
17 changed files with 21 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/CODING-GUIDELINES
View File

@@ -22,7 +22,7 @@ lines, and is well documented.
Asterisk is published under a dual-licensing scheme by Digium.
To be accepted into the codebase, all non-trivial changes must be
licensed to Digium. For more information, see the electronic license
agreement on http://bugs.digium.com/.
agreement on https://issues.asterisk.org/.
Patches should be in the form of a unified (-u) diff, made from a checkout
from subversion.

2
doc/asterisk.8
View File

@@ -176,7 +176,7 @@ supplied.
\fBasterisk -rx "core show channels"\fR - Display channels on running server
.SH "BUGS"
.PP
Bug reports and feature requests may be filed at http://bugs.digium.com
Bug reports and feature requests may be filed at https://issues.asterisk.org
.SH "SEE ALSO"
.PP
*CLI> \fBhelp\fR - Help on Asterisk CLI

2
doc/asterisk.sgml
View File

@@ -327,7 +327,7 @@
<refsect1>
<title>BUGS</title>
<para>
Bug reports and feature requests may be filed at http://bugs.digium.com
Bug reports and feature requests may be filed at https://issues.asterisk.org
</para>
</refsect1>
<refsect1>

2
doc/backtrace.txt
View File

@@ -1,6 +1,6 @@
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
https://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

2
doc/tex/backtrace.tex
View File

@@ -1,6 +1,6 @@
This document is intended to provide information on how to obtain the
backtraces required on the asterisk bug tracker, available at
\url{http://bugs.digium.com}. The information is required by developers to
\url{https://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

2
doc/tex/misdn.tex
View File

@@ -247,7 +247,7 @@ parts. mISDN Debug messages begin with an 'I', Asterisk messages begin with
an '*', the rest is clear I think.
Please take a trace of the problem and open a report in the Asterisk issue
tracker at \url{http://bugs.digium.com} in the "channel drivers" project,
tracker at \url{https://issues.asterisk.org} in the "channel drivers" project,
"chan\_misdn" category. Read the bug guidelines to make sure you
provide all the information needed.

2
doc/tex/mp3.tex
View File

@@ -7,5 +7,5 @@ music on hold selections.
However, if you still need to use mp3 as your music on hold format, a format
driver for reading MP3 audio files is available in the asterisk-addons SVN
repository on svn.digium.com or in the asterisk-addons release at
\url{http://downloads.digium.com/pub/telephony/asterisk/}.
\url{http://downloads.asterisk.org/pub/telephony/asterisk/}.