]> git.ipfire.org Git - thirdparty/gcc.git/blame - .github/CONTRIBUTING.md
libstdc++: Fix "extact" typos in comments
[thirdparty/gcc.git] / .github / CONTRIBUTING.md
CommitLineData
2b9778c8
EG
1## Contributing to GCC
2
3Thanks for taking the time to contribute to GCC! Please be advised that if you are
4viewing this on `github.com`, that the mirror there is unofficial and unmonitored.
5The GCC community does not use `github.com` for their contributions. Instead, we use
6a mailing list (`gcc-patches@gcc.gnu.org`) for code submissions, code
7reviews, and bug reports.
8
4968e484
EG
9Perhaps one day it will be possible to use [GitGitGadget](https://gitgitgadget.github.io/)
10to conveniently send Pull Requests commits to GCC's mailing list, the way that the Git
11project currently allows it to be used to send PRs to their mailing list, but until that
12day arrives, please send your patches to the mailing list manually.
2b9778c8 13
4968e484
EG
14Please read ["Contributing to GCC"](https://gcc.gnu.org/contribute.html) on the main GCC
15website to learn how the GCC project is managed, and how you can work with it.
16In addition, we highly recommend you to read
17[our guidelines for read-write Git access](https://gcc.gnu.org/gitwrite.html).
2b9778c8 18
4968e484
EG
19Or, you can follow the
20["Contributing to GCC in 10 easy steps"](https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps)
21section of the ["Getting Started" page](https://gcc.gnu.org/wiki/GettingStarted) on
22[the wiki](https://gcc.gnu.org/wiki) for another example of the contribution process.
2b9778c8
EG
23
24Your friendly GCC community!