Update repo location

Author: brson

CONTRIBUTING.md

@@ -20,13 +20,13 @@ please do two things:
 
 Pull requests will be treated as "review requests", and we will give
 feedback we expect to see corrected on
-[style](https://github.com/mozilla/rust/wiki/Note-style-guide) and
+[style](https://github.com/rust-lang/rust/wiki/Note-style-guide) and
 substance before pulling.  Changes contributed via pull request should
 focus on a single issue at a time, like any other.  We will not accept
 pull-requests that try to "sneak" unrelated changes in.
 
 Normally, all pull requests must include regression tests (see
-[Note-testsuite](https://github.com/mozilla/rust/wiki/Note-testsuite))
+[Note-testsuite](https://github.com/rust-lang/rust/wiki/Note-testsuite))
 that test your change.  Occasionally, a change will be very difficult
 to test for.  In those cases, please include a note in your commit
 message explaining why.
@@ -41,4 +41,4 @@ example, if it's 2014, and you change a Rust file that was created in
 ```
 
 For more details, please refer to
-[Note-development-policy](https://github.com/mozilla/rust/wiki/Note-development-policy).
+[Note-development-policy](https://github.com/rust-lang/rust/wiki/Note-development-policy).

Makefile.in

@@ -98,8 +98,8 @@
 # This is hardly all there is to know of The Rust Build System's
 # mysteries. The tale continues on the wiki[1][2].
 #
-# [1]: https://github.com/mozilla/rust/wiki/Note-build-system
-# [2]: https://github.com/mozilla/rust/wiki/Note-testsuite
+# [1]: https://github.com/rust-lang/rust/wiki/Note-build-system
+# [2]: https://github.com/rust-lang/rust/wiki/Note-testsuite
 #
 # If you really feel like getting your hands dirty, then:
 #

README.md

@@ -14,8 +14,8 @@ documentation.
 
 [installer]: http://www.rust-lang.org/install.html
 [tutorial]: http://doc.rust-lang.org/tutorial.html
-[wiki-start]: https://github.com/mozilla/rust/wiki/Note-getting-started-developing-Rust
-[win-wiki]: https://github.com/mozilla/rust/wiki/Using-Rust-on-Windows
+[wiki-start]: https://github.com/rust-lang/rust/wiki/Note-getting-started-developing-Rust
+[win-wiki]: https://github.com/rust-lang/rust/wiki/Using-Rust-on-Windows
 
 ## Building from Source
 
@@ -38,7 +38,7 @@ documentation.
 
     Or to build from the [repo] do:
 
-        $ git clone https://github.com/mozilla/rust.git
+        $ git clone https://github.com/rust-lang/rust.git
         $ cd rust
 
     Now that you have Rust's source code, you can configure and build it:
@@ -58,7 +58,7 @@ documentation.
 3. Read the [tutorial].
 4. Enjoy!
 
-[repo]: https://github.com/mozilla/rust
+[repo]: https://github.com/rust-lang/rust
 [tarball]: http://static.rust-lang.org/dist/rust-nightly.tar.gz
 [tutorial]: http://doc.rust-lang.org/tutorial.html
 
@@ -83,7 +83,7 @@ swap, it will take a very long time to build.
 
 There is a lot more documentation in the [wiki].
 
-[wiki]: https://github.com/mozilla/rust/wiki
+[wiki]: https://github.com/rust-lang/rust/wiki
 
 ## License
 

man/rustc.1

@@ -184,7 +184,7 @@ To build an executable with debug info:
 rustdoc
 
 .SH "BUGS"
-See <\fBhttps://github.com/mozilla/rust/issues\fR> for issues.
+See <\fBhttps://github.com/rust-lang/rust/issues\fR> for issues.
 
 .SH "AUTHOR"
 See \fBAUTHORS.txt\fR in the Rust source distribution.

man/rustdoc.1

@@ -87,7 +87,7 @@ The generated HTML can be viewed with any standard web browser.
 rustc
 
 .SH "BUGS"
-See <\fBhttps://github.com/mozilla/rust/issues\fR> for issues.
+See <\fBhttps://github.com/rust-lang/rust/issues\fR> for issues.
 
 .SH "AUTHOR"
 See \fBAUTHORS.txt\fR in the Rust source distribution.

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

src/doc/complement-design-faq.md

@@ -111,7 +111,7 @@ match val.do_something() {
 [#3101][iss] is the issue that proposed making this the only behavior, with
 rationale and discussion.
 
-[iss]: https://github.com/mozilla/rust/issues/3101
+[iss]: https://github.com/rust-lang/rust/issues/3101
 
 ## No guaranteed tail-call optimization
 

src/doc/complement-lang-faq.md

@@ -5,9 +5,9 @@
 
 There aren't many large programs yet. The Rust [compiler][rustc], 60,000+ lines at the time of writing, is written in Rust. As the oldest body of Rust code it has gone through many iterations of the language, and some parts are nicer to look at than others. It may not be the best code to learn from, but [borrowck] and [resolve] were written recently.
 
-[rustc]: https://github.com/mozilla/rust/tree/master/src/librustc
-[resolve]: https://github.com/mozilla/rust/blob/master/src/librustc/middle/resolve.rs
-[borrowck]: https://github.com/mozilla/rust/blob/master/src/librustc/middle/borrowck/
+[rustc]: https://github.com/rust-lang/rust/tree/master/src/librustc
+[resolve]: https://github.com/rust-lang/rust/blob/master/src/librustc/middle/resolve.rs
+[borrowck]: https://github.com/rust-lang/rust/blob/master/src/librustc/middle/borrowck/
 
 A research browser engine called [Servo][servo], currently 30,000+ lines across more than a dozen crates, will be exercising a lot of Rust's distinctive type-system and concurrency features, and integrating many native libraries.
 
@@ -21,9 +21,9 @@ Some examples that demonstrate different aspects of the language:
 * The extra library's [json] module. Enums and pattern matching
 
 [sprocketnes]: https://github.com/pcwalton/sprocketnes
-[hash]: https://github.com/mozilla/rust/blob/master/src/libstd/hash/mod.rs
-[HashMap]: https://github.com/mozilla/rust/blob/master/src/libcollections/hashmap.rs
-[json]: https://github.com/mozilla/rust/blob/master/src/libserialize/json.rs
+[hash]: https://github.com/rust-lang/rust/blob/master/src/libstd/hash/mod.rs
+[HashMap]: https://github.com/rust-lang/rust/blob/master/src/libcollections/hashmap.rs
+[json]: https://github.com/rust-lang/rust/blob/master/src/libserialize/json.rs
 
 You may also be interested in browsing [GitHub's Rust][github-rust] page.
 
@@ -33,8 +33,8 @@ You may also be interested in browsing [GitHub's Rust][github-rust] page.
 
 Yes. All development happens in lock-step on all 3 target platforms. Using MinGW, not Cygwin. Note that the windows implementation currently has some limitations: in particular 64-bit build is [not fully supported yet][win64], and all executables created by rustc [depends on libgcc DLL at runtime][libgcc].
 
-[win64]: https://github.com/mozilla/rust/issues/1237
-[libgcc]: https://github.com/mozilla/rust/issues/11782
+[win64]: https://github.com/rust-lang/rust/issues/1237
+[libgcc]: https://github.com/rust-lang/rust/issues/11782
 
 ## Is it OO? How do I do this thing I normally do in an OO language?
 

src/doc/index.md

@@ -75,4 +75,4 @@ li {list-style-type: none; }
     * [`#rust-internals`](http://chat.mibbit.com/?server=irc.mozilla.org&channel=%23rust-internals) - compiler and libraries
     * [`#rust-osdev`](http://chat.mibbit.com/?server=irc.mozilla.org&channel=%23rust-osdev) - operating system development
 * The Rust community on [Reddit](http://reddit.com/r/rust)
-* The Rust [wiki](http://github.com/mozilla/rust/wiki)
+* The Rust [wiki](http://github.com/rust-lang/rust/wiki)

src/doc/intro.md

@@ -361,7 +361,7 @@ fn main() {
 
             // This is ugly for now, but will be replaced by
             // `numbers[num as uint] += 1` in the near future.
-            // See: https://github.com/mozilla/rust/issues/6515
+            // See: https://github.com/rust-lang/rust/issues/6515
             *numbers.get_mut(num as uint) = *numbers.get_mut(num as uint) + 1;
 
             println!("{}", *numbers.get(num as uint));