mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-04-22 15:32:14 +02:00
Code Issues Packages Projects Releases Wiki Activity

documentation: Section Heading change for pushing commits

Browse Source 
Changed the section heading for the part describing how to
push changes upstream via the poky scripts.  Also had to
change one cross-reference to the section in the kernel
manual.

(From yocto-docs rev: be7712aba044238e8781cdf869c5d14e77eb09a2)

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 14:55:23 -07:00
committed by Richard Purdie
parent 0c69e7be91
commit 6b357655fe
2 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
documentation/dev-manual/dev-manual-newbie.xml
View File

@@ -987,11 +987,11 @@
your detailed description.
For example, the Yocto Project uses a specific convention for bug
references - any commit that addresses a specific bug should include the
bug ID in the description (typically at the end) as follows:
bug ID in the description (typically at the beginning) as follows:
<literallayout class='monospaced'>
&lt;detailed description of change&gt;
[YOCTO #&lt;bug-id&gt;]
&lt;detailed description of change&gt;
</literallayout></para></listitem>
Where &lt;bug-id&gt; is replaced with the specific bug ID from the
Yocto Project Bugzilla instance.
@@ -1009,7 +1009,7 @@
</para>
<section id='pushing-a-change-upstream'>
<title>Pushing a Change Upstream and Requesting a Pull</title>
<title>Using Scripts to Push a Change Upstream and Request a Pull</title>
<para>
The basic flow for pushing a change to an upstream "contrib" Git repository is as follows:
@@ -1100,8 +1100,8 @@
see <filename>GIT_FORMAT_PATCH(1)</filename> displayed using the
<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
method described in the "<link linkend='pushing-a-change-upstream'>Using Scripts to Push
a change Upstream and Request 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

4
documentation/kernel-manual/kernel-how-to.xml
View File

@@ -369,8 +369,8 @@
The Yocto Project provides scripts that help you work in a collaborative development
environment.
For information on these scripts, see the
"<ulink url='&YOCTO_DOCS_DEV_URL;#pushing-a-change-upstream'>Pushing a Change
Upstream and Requesting a Pull</ulink>" and
"<ulink url='&YOCTO_DOCS_DEV_URL;#pushing-a-change-upstream'>Using Scripts to Push a Change
Upstream and Request a Pull</ulink>" and
"<ulink url='&YOCTO_DOCS_DEV_URL;#submitting-a-patch'>Submitting a Patch Through
Email</ulink>" sections in the Yocto Project Development Manual.
</para>