sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Edits to "Using a Quilt Workflow" section. 

(From yocto-docs rev: 392cfbab010858ce0354a41e1e6c2304a3be9287)

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 2013-04-10 15:00:08 -07:00 committed by Richard Purdie
parent 5d69e33502
commit d5084b2732
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
documentation/dev-manual/dev-manual-model.xml
View File

@ -1696,7 +1696,7 @@
$ bitbake -c compile -f &lt;name_of_package&gt; $ bitbake -c compile -f &lt;name_of_package&gt;
</literallayout> </literallayout>
The <filename>-f</filename> or <filename>--force</filename> The <filename>-f</filename> or <filename>--force</filename>
option forces re-execution of the specified task. option forces the specified task to execute.
If you find problems with your code, you can just keep editing and If you find problems with your code, you can just keep editing and
re-testing iteratively until things work as expected. re-testing iteratively until things work as expected.
<note>All the modifications you make to the temporary source code <note>All the modifications you make to the temporary source code
@ -1713,7 +1713,7 @@
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ quilt refresh $ quilt refresh
</literallayout> </literallayout>
At this point the <filename>my_changes.patch</filename> file has all your edits made At this point, the <filename>my_changes.patch</filename> file has all your edits made
to the <filename>file1.c</filename>, <filename>file2.c</filename>, and to the <filename>file1.c</filename>, <filename>file2.c</filename>, and
<filename>file3.c</filename> files.</para> <filename>file3.c</filename> files.</para>
<para>You can find the resulting patch file in the <filename>patches/</filename> <para>You can find the resulting patch file in the <filename>patches/</filename>