summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2015-05-10 11:19:55 +0200
committerMichael Kerrisk <mtk.manpages@gmail.com>2015-05-10 11:19:55 +0200
commit7c862a16a50e57d6dfb39117e8a693d8b91b80ca (patch)
treeab5d8f59ab6508a62b08fb4418ea3f833a121663
parentb6143cbd8bde624091daa67ff52f4326cb268ff9 (diff)
downloadwebsite-7c862a16a50e57d6dfb39117e8a693d8b91b80ca.tar.gz
Update glibc bugzilla address
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
-rw-r--r--reporting_code_bugs.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/reporting_code_bugs.html b/reporting_code_bugs.html
index eb7bd66..696b608 100644
--- a/reporting_code_bugs.html
+++ b/reporting_code_bugs.html
@@ -50,7 +50,7 @@ Linux <em>man-pages</em>: &nbsp;
If you are reasonably sure that your bug is not a result of
distribution-specific modifications to glibc, then you can
submit a bug to the
- <a href="http://sources.redhat.com/bugzilla/">glibc bugzilla</a>.
+ <a href="https://sourceware.org/bugzilla/">glibc bugzilla</a>.
If the glibc bug is distribution-specific,
then raise a report in your distributor's bug-reporting facility:
if necessary, the distributor will push the bug upstream to the