diff options
| author | Eric Gallager <egallager@gcc.gnu.org> | 2023-11-01 19:28:56 -0400 |
|---|---|---|
| committer | Eric Gallager <egallager@gcc.gnu.org> | 2023-11-01 19:28:56 -0400 |
| commit | 4968e4844a3ce30143ae2e267895c418f5c636a1 (patch) | |
| tree | 87cda0151a34ecf4cb0e96c339fda0b894ab44cc | |
| parent | 2b9778c8d9d33174de63716b74b2f114d700e104 (diff) | |
| download | gcc-4968e4844a3ce30143ae2e267895c418f5c636a1.zip gcc-4968e4844a3ce30143ae2e267895c418f5c636a1.tar.gz gcc-4968e4844a3ce30143ae2e267895c418f5c636a1.tar.bz2 | |
Minor formatting fix for newly-added file from previous commit
Committing under the "obvious" rule.
ChangeLog:
* .github/CONTRIBUTING.md: Wrap lines more tightly.
| -rw-r--r-- | .github/CONTRIBUTING.md | 18 |
1 files changed, 12 insertions, 6 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 4f7b3ab..d218924 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -6,13 +6,19 @@ The GCC community does not use `github.com` for their contributions. Instead, we a mailing list (`gcc-patches@gcc.gnu.org`) for code submissions, code reviews, and bug reports. -Perhaps one day it will be possible to use [GitGitGadget](https://gitgitgadget.github.io/) to -conveniently send Pull Requests commits to GCC's mailing list, the way that the Git project currently allows it to be used to send PRs to their mailing list, but until that day arrives, please send your patches to the mailing list manually. +Perhaps one day it will be possible to use [GitGitGadget](https://gitgitgadget.github.io/) +to conveniently send Pull Requests commits to GCC's mailing list, the way that the Git +project currently allows it to be used to send PRs to their mailing list, but until that +day arrives, please send your patches to the mailing list manually. -Please read ["Contributing to GCC"](https://gcc.gnu.org/contribute.html) on the main GCC website -to learn how the GCC project is managed, and how you can work with it. -In addition, we highly recommend you to read [our guidelines for read-write Git access](https://gcc.gnu.org/gitwrite.html). +Please read ["Contributing to GCC"](https://gcc.gnu.org/contribute.html) on the main GCC +website to learn how the GCC project is managed, and how you can work with it. +In addition, we highly recommend you to read +[our guidelines for read-write Git access](https://gcc.gnu.org/gitwrite.html). -Or, you can follow the ["Contributing to GCC in 10 easy steps"](https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps) section of the ["Getting Started" page](https://gcc.gnu.org/wiki/GettingStarted) on [the wiki](https://gcc.gnu.org/wiki) for another example of the contribution process. +Or, you can follow the +["Contributing to GCC in 10 easy steps"](https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps) +section of the ["Getting Started" page](https://gcc.gnu.org/wiki/GettingStarted) on +[the wiki](https://gcc.gnu.org/wiki) for another example of the contribution process. Your friendly GCC community! |