summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-07-03 14:12:26 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-07-04 14:48:17 +0100
commit75d007be846db36a1c87d566c30398357db018ff (patch)
tree37eeba452abd4a7fc55ae64e00edeaaa94717440
parentbf753f8aef0eb3d33d5950c45d319b3ed9486256 (diff)
downloadpoky-75d007be846db36a1c87d566c30398357db018ff.tar.gz
documentation/dev-manual/dev-manual-newbie.xml: edits to sending patch
The section that describes how to send a patch upstream via email did not have a good connection to the various mailing lists. I added some references to this section and also mentioned using the scripts if the user has many changes to commit. (From yocto-docs rev: ad75ae45420c43bda974d22b02094237b5c7cc50) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml22
1 files changed, 20 insertions, 2 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 09095981b3..4db4bc1441 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -1050,7 +1050,18 @@
1050 <para> 1050 <para>
1051 If you have a just few changes, you can commit them and then submit them as an 1051 If you have a just few changes, you can commit them and then submit them as an
1052 email to the maintainer. 1052 email to the maintainer.
1053 Here is a general procedure: 1053 Depending on the components changed, you need to submit the email to a specific
1054 mailing list.
1055 For some guidance on which mailing list to use, see the list in the
1056 "<link linkend='how-to-submit-a-change'>How to Submit a Change</link>" section
1057 earlier in this manual.
1058 For a description of the available mailing lists, see
1059 "<ulink url='&YOCTO_DOCS_REF_URL;#resources-mailinglist'>Mailing Lists</ulink>"
1060 section in the Yocto Project Reference Manual.
1061 </para>
1062
1063 <para>
1064 Here is the general procedure on how to submit a patch through email:
1054 <itemizedlist> 1065 <itemizedlist>
1055 <listitem><para>Make your changes in your local Git repository.</para></listitem> 1066 <listitem><para>Make your changes in your local Git repository.</para></listitem>
1056 <listitem><para>Stage your changes by using the <filename>git add</filename> 1067 <listitem><para>Stage your changes by using the <filename>git add</filename>
@@ -1087,7 +1098,14 @@
1087 the series of patches. 1098 the series of patches.
1088 For information on the <filename>git format-patch</filename> command, 1099 For information on the <filename>git format-patch</filename> command,
1089 see <filename>GIT_FORMAT_PATCH(1)</filename> displayed using the 1100 see <filename>GIT_FORMAT_PATCH(1)</filename> displayed using the
1090 <filename>man git-format-patch</filename> command.</para></listitem> 1101 <filename>man git-format-patch</filename> command.</para>
1102 <note>If you have many patches to submit, you might consider using the
1103 method described in the "<link linkend='pushing-a-change-upstream'>Pushing
1104 a change Upstream and Requesting a Pull</link>" section described
1105 earlier in the manual.
1106 This method uses the <filename>create-pull-request</filename> and
1107 <filename>send-pull-request</filename> scripts that automate much of the
1108 process.</note></listitem>
1091 <listitem><para>Import the files into your mail client by using the 1109 <listitem><para>Import the files into your mail client by using the
1092 <filename>git send-email</filename> command. 1110 <filename>git send-email</filename> command.
1093 <note>In order to use <filename>git send-email</filename>, you must have the 1111 <note>In order to use <filename>git send-email</filename>, you must have the