documentation: Section change for using email to submit patch

Changed the title and a single reference from the Kernel manual
to a title more representative of how these patches are sent -
not using scripts.

(From yocto-docs rev: ff908c34fae88eab9724891a008142a834f34081)

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:33:33 -07:00 committed by Richard Purdie
parent 2595a2b65e
commit d192e6f2ad
2 changed files with 3 additions and 3 deletions

View File

@ -1051,7 +1051,7 @@
</section> </section>
<section id='submitting-a-patch'> <section id='submitting-a-patch'>
<title>Submitting a Patch Through Email</title> <title>Using Email to Submit a Patch</title>
<para> <para>
If you have a just few changes, you can commit them and then submit them as an If you have a just few changes, you can commit them and then submit them as an

View File

@ -371,8 +371,8 @@
For information on these scripts, see the For information on these scripts, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#pushing-a-change-upstream'>Using Scripts to Push a Change "<ulink url='&YOCTO_DOCS_DEV_URL;#pushing-a-change-upstream'>Using Scripts to Push a Change
Upstream and Request a Pull</ulink>" and Upstream and Request a Pull</ulink>" and
"<ulink url='&YOCTO_DOCS_DEV_URL;#submitting-a-patch'>Submitting a Patch Through "<ulink url='&YOCTO_DOCS_DEV_URL;#submitting-a-patch'>Using Email to Submit a Patch</ulink>"
Email</ulink>" sections in the Yocto Project Development Manual. sections in the Yocto Project Development Manual.
</para> </para>
<para> <para>