mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-09 05:29:32 +00:00
Code Issues Projects Releases Wiki Activity

documentation/dev-manual/dev-manual-newbie.xml: edits to how to submit change section.

Browse Source 
(From yocto-docs rev: 16533369264deb5f93b0d97f0d8491ee45fe23db)

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
2011-07-22 10:26:01 -07:00
committed by Richard Purdie
parent 5c6753735f
commit 0e697a6c9e
1 changed files with 8 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/dev-manual/dev-manual-newbie.xml
+8 -9
View File
@@ -495,10 +495,9 @@
</para>
<para>
Sometimes you might find it necessary to submit a change or patch to the Yocto Project.
If so, you must follow certain procedures.
When you submit a change or patch to the Yocto Project you must follow certain procedures.
In particular, the headers in patches and the commit messages must follow a certain standard.
The general process is the same as described earlier in this section.
The general process is the same as described earlier in this chapter.
For complete details on how to create proper commit messages and patch headers see
[WRITER NOTE: I need the link to Mark's wiki page here that describes the process.]
</para>
@@ -511,17 +510,17 @@
<title>Pushing a Change Upstream</title>
<para>
The basic flow for pushing a change to an upstream contrib repository is as follows:
The basic flow for pushing a change to an upstream "contrib" Git repository is as follows:
<itemizedlist>
<listitem><para>Make your changes in your local repository.</para></listitem>
<listitem><para>Make your changes in your local Git repository.</para></listitem>
<listitem><para>Stage your commit (or change) by using the <filename>git add</filename>
command.</para></listitem>
<listitem><para>Commit the change by using the <filename>git commit</filename>
command and push it to an upstream contrib repository.
command and push it to the upstream "contrib" repository.
Be sure to provide a commit message that follows the project’s commit standards.</para></listitem>
<listitem><para>Notify the maintainer that you have pushed a change.</para></listitem>
</itemizedlist>
You can find detailed information on how to push a change upstream
You can find general Git information on how to push a change upstream
<ulink url='http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#Developing-With-git'>
here</ulink>.
</para>
@@ -534,7 +533,7 @@
If you have a just a few changes you can commit them and then submit them as an email to the maintainer.
Here is the general procedure:
<itemizedlist>
<listitem><para>Make your changes in your local repository.</para></listitem>
<listitem><para>Make your changes in your local Git repository.</para></listitem>
<listitem><para>Stage your commit (or change) by using the <filename>git add</filename>
command.</para></listitem>
<listitem><para>Commit the change by using the <filename>git commit</filename> command.
@@ -549,7 +548,7 @@
</itemizedlist>
Be aware that there could be protocols and standards that you need to follow for your particular
project.
You can find detailed information on the general process
You can find general Git information for submitting a patch
<ulink url='http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#sharing-development'>
here</ulink>.
</para>