From d192e6f2ad28e4c4ca3e19086da6f5927c71fc35 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 24 Aug 2012 15:33:33 -0700 Subject: 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 Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-newbie.xml | 2 +- documentation/kernel-manual/kernel-how-to.xml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'documentation') 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 @@
- Submitting a Patch Through Email + Using Email to Submit a Patch 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 @@ For information on these scripts, see the "Using Scripts to Push a Change Upstream and Request a Pull" and - "Submitting a Patch Through - Email" sections in the Yocto Project Development Manual. + "Using Email to Submit a Patch" + sections in the Yocto Project Development Manual. -- cgit v1.2.3-54-g00ecf