about summary refs log tree commit diff
diff options
context:
space:
mode:
authorGraydon Hoare <graydon@pobox.com>2013-06-13 15:41:34 -0600
committerGraydon Hoare <graydon@pobox.com>2013-06-13 15:41:34 -0600
commitb417bc8511a0a38e73312cee8086ed04eeb21b75 (patch)
treefde5a7ff0f75fde98941fc3de0d878e0e63fefaf
parent541c657a738006d78171aa261125a6a46f283b35 (diff)
downloadrust-b417bc8511a0a38e73312cee8086ed04eeb21b75.tar.gz
rust-b417bc8511a0a38e73312cee8086ed04eeb21b75.zip
Update CONTRIBUTING.md
-rw-r--r--CONTRIBUTING.md8
1 files changed, 2 insertions, 6 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 3cba6f2891a..56be6c3ec78 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,15 +1,11 @@
 ## Pull request procedure
 
-Pull requests should be targeted at Rust's `incoming` branch (note
-that by default Github will aim them at the `master` branch) -- see
-"Changing The Commit Range and Destination Repository" in Github's
-documentation on [pull
-requests](https://help.github.com/articles/using-pull-requests).
+Pull requests should be targeted at Rust's `master` branch.
 Before pushing to your Github repo and issuing the pull request,
 please do two things:
 
 1. [Rebase](http://git-scm.com/book/en/Git-Branching-Rebasing) your
-   local changes against the `incoming` branch. Resolve any conflicts
+   local changes against the `master` branch. Resolve any conflicts
    that arise.
 
 2. Run the full Rust test suite with the `make check` command.  You're