servo: Merge #5908 - Use canonical Servo GitHub URLs (from dhodder:master); r=jdm
authorDave Hodder <dmh@dmh.org.uk>
Thu, 30 Apr 2015 13:00:42 -0500
changeset 382936 ac1a2d43bd8ea4eb5ea4103f2a039ec003519cf0
parent 382935 5455270ea085a0f4dc8924b201cdbe2562a2e549
child 382937 3ac3db2cf2a3f01a80afe13dd85e764f5b25a33a
push id7198
push userjlorenzo@mozilla.com
push dateTue, 18 Apr 2017 12:07:49 +0000
treeherdermozilla-beta@d57aa49c3948 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersjdm
servo: Merge #5908 - Use canonical Servo GitHub URLs (from dhodder:master); r=jdm Three URLs have changed from `github.com/mozilla/servo` to `github.com/servo/servo`. Source-Repo: https://github.com/servo/servo Source-Revision: 826b7222027b7b8b5df417998a1e4826aecb019a
servo/CONTRIBUTING.md
--- a/servo/CONTRIBUTING.md
+++ b/servo/CONTRIBUTING.md
@@ -7,36 +7,36 @@ thinking of helping us:
 ## Contributions
 
 Contributions to Servo or its dependencies should be made in the form of GitHub
 pull requests. Each pull request will be reviewed by a core contributor
 (someone with permission to land patches) and either landed in the main tree or
 given feedback for changes that would be required. All contributions should
 follow this format, even those from core contributors.
 
-If you're looking for easy bugs, have a look at the [E-Easy issue tag](https://github.com/mozilla/servo/issues?labels=E-easy&page=1&state=open) on GitHub.
+If you're looking for easy bugs, have a look at the [E-Easy issue tag](https://github.com/servo/servo/labels/E-easy) on GitHub.
 
 ## Pull Request Checklist
 
 - Branch from the master branch and, if needed, rebase to the current master
   branch before submitting your pull request. If it doesn't merge cleanly with
   master you may be asked to rebase your changes.
 
 - Don't put submodule updates in your pull request unless they are to landed
   commits.
 
 - If your patch is not getting reviewed or you need a specific person to review
   it, you can @-reply a reviewer asking for a review in the pull request or a
   comment, or you can ask for a review in `#servo` on `irc.mozilla.org`.
 
 - Add tests relevant to the fixed bug or new feature.  For a DOM change this
   will usually be a web platform test; for layout, a reftest.  See our [testing
-  guide](https://github.com/mozilla/servo/wiki/Testing) for more information.
+  guide](https://github.com/servo/servo/wiki/Testing) for more information.
 
-For specific git instructions, see [GitHub & Critic PR handling 101](https://github.com/mozilla/servo/wiki/Github-&-Critic-PR-handling-101).
+For specific git instructions, see [GitHub & Critic PR handling 101](https://github.com/servo/servo/wiki/Github-&-Critic-PR-handling-101).
 
 ## Conduct
 
 We follow the [Rust Code of Conduct](http://www.rust-lang.org/conduct.html).
 
 
 ## Communication