summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-08-24 15:33:33 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-09-04 12:55:00 +0100
commitd192e6f2ad28e4c4ca3e19086da6f5927c71fc35 (patch)
tree36fb95a4c0b0df8070e2509fd826b390553c8b88 /documentation
parent2595a2b65e843d9d7786143b1fdd16b076ed4e91 (diff)
downloadpoky-d192e6f2ad28e4c4ca3e19086da6f5927c71fc35.tar.gz
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>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-newbie.xml2
-rw-r--r--documentation/kernel-manual/kernel-how-to.xml4
2 files changed, 3 insertions, 3 deletions
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 8ab6ecf662..3d6ee9c8bc 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -1051,7 +1051,7 @@
1051 </section> 1051 </section>
1052 1052
1053 <section id='submitting-a-patch'> 1053 <section id='submitting-a-patch'>
1054 <title>Submitting a Patch Through Email</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 If you have a just few changes, you can commit them and then submit them as an
diff --git a/documentation/kernel-manual/kernel-how-to.xml b/documentation/kernel-manual/kernel-how-to.xml
index a44e5ea51e..f470d3e7d2 100644
--- a/documentation/kernel-manual/kernel-how-to.xml
+++ b/documentation/kernel-manual/kernel-how-to.xml
@@ -371,8 +371,8 @@
371 For information on these scripts, see the 371 For information on these scripts, see the
372 "<ulink url='&YOCTO_DOCS_DEV_URL;#pushing-a-change-upstream'>Using Scripts to Push a Change 372 "<ulink url='&YOCTO_DOCS_DEV_URL;#pushing-a-change-upstream'>Using Scripts to Push a Change
373 Upstream and Request a Pull</ulink>" and 373 Upstream and Request a Pull</ulink>" and
374 "<ulink url='&YOCTO_DOCS_DEV_URL;#submitting-a-patch'>Submitting a Patch Through 374 "<ulink url='&YOCTO_DOCS_DEV_URL;#submitting-a-patch'>Using Email to Submit a Patch</ulink>"
375 Email</ulink>" sections in the Yocto Project Development Manual. 375 sections in the Yocto Project Development Manual.
376 </para> 376 </para>
377 377
378 <para> 378 <para>