OpenE2K/rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Rollup merge of #48705 - klnusbaum:update_rfc_process, r=aturon

Browse Source 
Update Feature Request instructions

As noted in #48393 the contribution instructions for submitting a Feature Request are a little hasty, suggesting that the user immediately create an issue in the RFC repository. For users that want to submit a feature request, let's instead point them directly to the README file for the RFC repository, which contains detailed instructions on how to submit a Feature Request.
This commit is contained in:
kennytm 2018-03-13 00:54:25 +08:00 committed by GitHub
commit 7bd8f6ea31
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
CONTRIBUTING.md
View File

@ -26,10 +26,10 @@ As a reminder, all contributors are expected to follow our [Code of Conduct][coc
## Feature Requests ## Feature Requests
[feature-requests]: #feature-requests [feature-requests]: #feature-requests
To request a change to the way that the Rust language works, please open an To request a change to the way the Rust language works, please head over
issue in the [RFCs repository](https://github.com/rust-lang/rfcs/issues/new) to the [RFCs repository](https://github.com/rust-lang/rfcs) and view the
rather than this one. New features and other significant language changes [README](https://github.com/rust-lang/rfcs/blob/master/README.md)
must go through the RFC process. for instructions.
## Bug Reports ## Bug Reports
[bug-reports]: #bug-reports [bug-reports]: #bug-reports