about summary refs log tree commit diff
path: root/src/doc/complement-bugreport.md
diff options
context:
space:
mode:
authorBrian Anderson <banderson@mozilla.com>2014-06-16 16:07:34 -0700
committerAlex Crichton <alex@alexcrichton.com>2014-06-16 18:16:36 -0700
commitf4ae8a83f9e56a7f16a5f0a25d22c74063e2fb5e (patch)
tree095cf0cff432afd4cb528875690191fabb10df1a /src/doc/complement-bugreport.md
parente1971dd35a679ff8fc438f7ccb8d6754de472d6e (diff)
downloadrust-f4ae8a83f9e56a7f16a5f0a25d22c74063e2fb5e.tar.gz
rust-f4ae8a83f9e56a7f16a5f0a25d22c74063e2fb5e.zip
Update repo location
Diffstat (limited to 'src/doc/complement-bugreport.md')
-rw-r--r--src/doc/complement-bugreport.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/complement-bugreport.md b/src/doc/complement-bugreport.md
index d84d720871d..9057c135057 100644
--- a/src/doc/complement-bugreport.md
+++ b/src/doc/complement-bugreport.md
@@ -22,7 +22,7 @@ If you don't have enough time for a search, then don't worry about that. Just su
 the bug. If it's a duplicate, somebody will notice that and close it during triage.
 
 If you have the time for it, it would be useful to type the text of the error
-message you got [into the issue tracker search box](https://github.com/mozilla/rust/issues)
+message you got [into the issue tracker search box](https://github.com/rust-lang/rust/issues)
 to see if there's an existing bug that resembles your problem. If there is,
 and it's an open bug, you can comment on that issue and say you are also affected.
 This will encourage the devs to fix it. But again, don't let this stop you from