1This guide explains what to do to send a GCC patch for review.23All the commands are supposed to be run in the folder where you cloned GCC.45```bash6./contrib/gcc-changelog/git_check_commit.py7```89You can provide a specific commit hash:1011```bash12./contrib/gcc-changelog/git_check_commit.py abdef7898913```1415a range:1617```bash18./contrib/gcc-changelog/git_check_commit.py HEAD~219```2021or even a comparison with a remote branch:2223```bash24./contrib/gcc-changelog/git_check_commit.py upstream/master..HEAD25```2627When there is no more errors, generate the git patch:2829```bash30git format-patch -1 `git rev-parse --short HEAD`31```3233Then you can run the remaining checks using:3435```bash36contrib/check_GNU_style.sh 0001-your-patch.patch37```3839When you have no more errors, you can send the `.patch` file to GCC by sending an40email to `gcc-patches@gcc.gnu.org` and to the relevant GCC mailing lists41depending on what your patch changes. You can find the list of the mailing lists42[here](https://gcc.gnu.org/lists.html).4344You can find more information about "contributing to GCC" [here](https://gcc.gnu.org/contribute.html).