summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorSean Bright <sean@malleable.com>2009-05-28 22:42:27 +0000
committerSean Bright <sean@malleable.com>2009-05-28 22:42:27 +0000
commitc772d5a0e696a75199528350be47d63550d63dda (patch)
tree02e8bed00c399d7aae635b58e6ca8dfda07589f0 /include
parent1d00714496002d30714c58da24200acee89167f7 (diff)
Update references to downloads.digium.com to its new URL.
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@197861 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'include')
-rw-r--r--include/asterisk/doxygen/releases.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/asterisk/doxygen/releases.h b/include/asterisk/doxygen/releases.h
index 07640dac4..c895d1c3c 100644
--- a/include/asterisk/doxygen/releases.h
+++ b/include/asterisk/doxygen/releases.h
@@ -169,7 +169,7 @@
* Commits to the Asterisk 1.2 branch should only address security issues or
* regressions introduced by previous security fixes. For a security issue, the
* commit should be accompanied by an
- * <a href="http://downloads.digium.com/pub/security/">Asterisk Security Advisory</a>
+ * <a href="http://downloads.asterisk.org/pub/security/">Asterisk Security Advisory</a>
* and an immediate release. When a commit goes in to fix a regression, the previous
* security advisory that is related to the change that introduced the bug should get
* updated to indicate that there is an updated version of the fix. A release should