documentation/dev-manual/dev-manual-newbie.xml: Updates to submitting patches

I added text to indicate that using the two scripts for generating
patches and requesting pulls is the preferred method to send
a patch.

(From yocto-docs rev: d6f036a91074dd00c51fe0f937224182fc801b3b)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2012-08-24 15:05:51 -07:00 committed by Richard Purdie
parent 6b357655fe
commit 2595a2b65e
1 changed files with 7 additions and 1 deletions

View File

@ -1005,7 +1005,8 @@
</para>
<para>
Following are general instructions for both pushing changes upstream and for submitting changes as patches.
Following are general instructions for both pushing changes upstream and for submitting
changes as patches.
</para>
<section id='pushing-a-change-upstream'>
@ -1029,6 +1030,11 @@
<filename>send-pull-request</filename>.
You can find these scripts in the <filename>scripts</filename> directory of the
Yocto Project file structure.</para>
<para>Using these scripts correctly formats the requests without introducing any
whitespace or HTML formatting.
The maintainer that receives your patches needs to be able to save and apply them
directly from your emails.
Using these scripts is the preferred method for sending patches.</para>
<para>For help on using these scripts, simply provide the
<filename>-h</filename> argument as follows:
<literallayout class='monospaced'>