Skip to content

Commit bc4c1ef

Browse files
bors[bot]philberty
andauthored
Merge #455
455: Update CONTRIBUTING.md r=philberty a=philberty 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: Philip Herron <[email protected]>
2 parents 1f1d9ed + 8564e93 commit bc4c1ef

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,17 @@
66

77
* 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.
88

9-
#### **Did you write a patch that fixes a bug?**
9+
#### **Do you want to submit a patch?**
1010

1111
* Open a new GitHub pull request with the patch.
1212

1313
* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
1414

1515
* Before submitting, GCCRS requires copyright assignment. Please read the [Contributing to GCC](https://gcc.gnu.org/contribute.html) guide to know more.
1616

17+
* Patches sent to the [`gcc-rust` mailing list](https://gcc.gnu.org/mailman/listinfo/gcc-rust) are likewise welcome.
18+
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.
19+
1720
#### **Do you intend to add a new feature or change an existing one?**
1821

1922
* Suggest your change in the [Zulip](https://gcc-rust.zulipchat.com/) and start writing code.

0 commit comments

Comments
 (0)