File tree Expand file tree Collapse file tree 1 file changed +26
-0
lines changed Expand file tree Collapse file tree 1 file changed +26
-0
lines changed Original file line number Diff line number Diff line change
1
+ This guide explains what to do to send a GCC patch for review.
2
+
3
+ All the commands are supposed to be run in the folder where you cloned GCC.
4
+
5
+ ``` bash
6
+ ./contrib/gcc-changelog/git_check_commit.py
7
+ ```
8
+
9
+ When there is no more errors, generate the git patch:
10
+
11
+ ``` bash
12
+ git format-patch -1 ` git rev-parse --short HEAD`
13
+ ```
14
+
15
+ Then you can run the remaining checks using:
16
+
17
+ ``` bash
18
+ contrib/check_GNU_style.sh 0001-your-patch.patch
19
+ ```
20
+
21
+ When you have no more errors, you can send the ` .patch ` file to GCC by sending an
22
+ email to
` [email protected] ` and to the relevant GCC mailing lists
23
+ depending on what your patch changes. You can find the list of the mailing lists
24
+ [ here] ( https://gcc.gnu.org/lists.html ) .
25
+
26
+ You can find more information about "contributing to GCC" [ here] ( https://gcc.gnu.org/contribute.html ) .
You can’t perform that action at this time.
0 commit comments