KJ16609/gcc
1
0
Fork 0
mirror of https://gcc.gnu.org/git/gcc.git synced 2026-02-22 12:00:03 -05:00
Code Issues Packages Projects Releases Wiki Activity

Update CONTRIBUTING.md

Browse Source 
We have been accepting patches via mail from developers following the normal GCC processes. Let's update our guidelines to reflect this.

Co-authored-by: CohenArthur <arthur.cohen@epita.fr>
Co-authored-by: Thomas Schwinge <thomas@codesourcery.com>
Co-authored-by: Miguel Ojeda <ojeda@users.noreply.github.com>
This commit is contained in:
Philip Herron
2021-05-28 13:22:12 +01:00
parent 1f1d9ed87d
commit 8564e93111
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
CONTRIBUTING.md
View File

@@ -6,7 +6,7 @@
* If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/Rust-GCC/gccrs/issues/new). Be sure to include a **title and clear description**, as much relevant information as possible, and a **code sample** or an **executable test case** demonstrating the expected behavior that is not occurring.
#### **Did you write a patch that fixes a bug?**
#### **Do you want to submit a patch?**
* Open a new GitHub pull request with the patch.
@@ -14,6 +14,9 @@
* Before submitting, GCCRS requires copyright assignment. Please read the [Contributing to GCC](https://gcc.gnu.org/contribute.html) guide to know more.
* Patches sent to the [`gcc-rust` mailing list](https://gcc.gnu.org/mailman/listinfo/gcc-rust) are likewise welcome.
These will be imported into a GitHub PR to follow the normal review process, and the link to the GitHub PR sent to the submitter.
#### **Do you intend to add a new feature or change an existing one?**
* Suggest your change in the [Zulip](https://gcc-rust.zulipchat.com/) and start writing code.