GCC allows for the DCO sign-off.

This updates the contributor guide to let people know the update applys to
gccrs.

Co-authored-by: CohenArthur <arthur.cohen@epita.fr>
Co-authored-by: Marc Poulhiès <dkm@kataplop.net>
This commit is contained in:
Philip Herron 2021-10-13 10:33:29 +01:00
parent 3057d98a4e
commit 535a824bf7
2 changed files with 4 additions and 3 deletions

View File

@ -8,7 +8,7 @@ in the git commit message.
Here is a checklist to help you with your PR.
- \[ ] GCC code require copyright assignment: https://gcc.gnu.org/contribute.html
- \[ ] GCC development requires the DCO or copyright assignment. See: https://gcc.gnu.org/contribute.html or https://gcc.gnu.org/dco.html
- \[ ] Read contributing guidlines
- \[ ] `make check-rust` passes locally
- \[ ] Run `clang-format`
@ -18,4 +18,5 @@ Note that you can skip the above if you are just opening a WIP PR in
order to get feedback.
---
*Please write a short comment explaining your change.
*Please write a comment explaining your change. This is the message
that will be part of the merge commit.

View File

@ -12,7 +12,7 @@
* Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
* Before submitting, GCCRS requires copyright assignment. Please read the [Contributing to GCC](https://gcc.gnu.org/contribute.html) guide to know more.
* Before submitting, GCC development requires copyright assignment or the Developer's Certificate of Origin sign-off. Please read the [Contributing to GCC guide](https://gcc.gnu.org/contribute.html) or [DCO Guide](https://gcc.gnu.org/dco.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.