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>

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 @@
         <para>
             If you have a just few changes, you can commit them and then submit them as an 
             email to the maintainer.
-            Here is a general procedure:
+            Depending on the components changed, you need to submit the email to a specific
+            mailing list.
+            For some guidance on which mailing list to use, see the list in the 
+            "<link linkend='how-to-submit-a-change'>How to Submit a Change</link>" section
+            earlier in this manual.
+            For a description of the available mailing lists, see
+            "<ulink url='&YOCTO_DOCS_REF_URL;#resources-mailinglist'>Mailing Lists</ulink>"
+            section in the Yocto Project Reference Manual.
+        </para>
+
+        <para>            
+            Here is the general procedure on how to submit a patch through email:
             <itemizedlist>
                 <listitem><para>Make your changes in your local Git repository.</para></listitem>
                 <listitem><para>Stage your changes by using the <filename>git add</filename>
@@ -1087,7 +1098,14 @@
                     the series of patches.
                     For information on the <filename>git format-patch</filename> command, 
                     see <filename>GIT_FORMAT_PATCH(1)</filename> displayed using the  
-                    <filename>man git-format-patch</filename> command.</para></listitem>
+                    <filename>man git-format-patch</filename> command.</para>
+                    <note>If you have many patches to submit, you might consider using the 
+                    method described in the "<link linkend='pushing-a-change-upstream'>Pushing
+                    a change Upstream and Requesting a Pull</link>" section described 
+                    earlier in the manual.
+                    This method uses the <filename>create-pull-request</filename> and 
+                    <filename>send-pull-request</filename> scripts that automate much of the 
+                    process.</note></listitem>
                 <listitem><para>Import the files into your mail client by using the 
                     <filename>git send-email</filename> command.
                     <note>In order to use <filename>git send-email</filename>, you must have the