diff options
-rw-r--r-- | documentation/dev-manual/dev-manual-newbie.xml | 24 |
1 files changed, 11 insertions, 13 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml index 3d6ee9c8bc..96d6829d3e 100644 --- a/documentation/dev-manual/dev-manual-newbie.xml +++ b/documentation/dev-manual/dev-manual-newbie.xml | |||
@@ -1054,8 +1054,12 @@ | |||
1054 | <title>Using Email to Submit a Patch</title> | 1054 | <title>Using Email to Submit a Patch</title> |
1055 | 1055 | ||
1056 | <para> | 1056 | <para> |
1057 | If you have a just few changes, you can commit them and then submit them as an | 1057 | You can submit patches without using the <filename>create-pull-request</filename> and |
1058 | email to the maintainer. | 1058 | <filename>send-pull-request</filename> scripts described in the previous section. |
1059 | Keep in mind, the preferred method is to use the scripts, however. | ||
1060 | </para> | ||
1061 | |||
1062 | <para> | ||
1059 | Depending on the components changed, you need to submit the email to a specific | 1063 | Depending on the components changed, you need to submit the email to a specific |
1060 | mailing list. | 1064 | mailing list. |
1061 | For some guidance on which mailing list to use, see the list in the | 1065 | For some guidance on which mailing list to use, see the list in the |
@@ -1067,7 +1071,8 @@ | |||
1067 | </para> | 1071 | </para> |
1068 | 1072 | ||
1069 | <para> | 1073 | <para> |
1070 | Here is the general procedure on how to submit a patch through email: | 1074 | Here is the general procedure on how to submit a patch through email without using the |
1075 | scripts: | ||
1071 | <itemizedlist> | 1076 | <itemizedlist> |
1072 | <listitem><para>Make your changes in your local Git repository.</para></listitem> | 1077 | <listitem><para>Make your changes in your local Git repository.</para></listitem> |
1073 | <listitem><para>Stage your changes by using the <filename>git add</filename> | 1078 | <listitem><para>Stage your changes by using the <filename>git add</filename> |
@@ -1105,16 +1110,9 @@ | |||
1105 | For information on the <filename>git format-patch</filename> command, | 1110 | For information on the <filename>git format-patch</filename> command, |
1106 | see <filename>GIT_FORMAT_PATCH(1)</filename> displayed using the | 1111 | see <filename>GIT_FORMAT_PATCH(1)</filename> displayed using the |
1107 | <filename>man git-format-patch</filename> command.</para> | 1112 | <filename>man git-format-patch</filename> command.</para> |
1108 | <note>If you have many patches to submit, you might consider using the | 1113 | <note>If you are or will be a frequent contributor to the Yocto Project |
1109 | method described in the "<link linkend='pushing-a-change-upstream'>Using Scripts to Push | 1114 | or to OpenEmbedded, you might consider requesting a contrib area and the |
1110 | a change Upstream and Request a Pull</link>" section described | 1115 | necessary associated rights.</note></listitem> |
1111 | earlier in the manual. | ||
1112 | This method uses the <filename>create-pull-request</filename> and | ||
1113 | <filename>send-pull-request</filename> scripts that automate much of the | ||
1114 | process. | ||
1115 | You might also consider requesting a contrib area and the associated rights | ||
1116 | needed if you become a regular contributor to either the Yocto Project or | ||
1117 | OpenEmbedded.</note></listitem> | ||
1118 | <listitem><para>Import the files into your mail client by using the | 1116 | <listitem><para>Import the files into your mail client by using the |
1119 | <filename>git send-email</filename> command. | 1117 | <filename>git send-email</filename> command. |
1120 | <note>In order to use <filename>git send-email</filename>, you must have the | 1118 | <note>In order to use <filename>git send-email</filename>, you must have the |