diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-02-22 12:54:29 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-03-08 12:08:00 -0800 |
| commit | a72bea5bf543b2bc99ede65396deab96c7d18df1 (patch) | |
| tree | 2333609efb0e5847442cffeba06a0d13d8b1ace8 /documentation/dev-manual | |
| parent | 8268a69c409f504a5cbdb8acd116ae0b99976cf4 (diff) | |
| download | ast2050-yocto-poky-a72bea5bf543b2bc99ede65396deab96c7d18df1.zip ast2050-yocto-poky-a72bea5bf543b2bc99ede65396deab96c7d18df1.tar.gz | |
documentation/dev-manual/dev-manual-common-tasks.xml: Review comments
Had to back off a bit on the use of the term "working directory".
Paul clarified that it was okay to use the term "temporary source code
location" when talking about where the source code for a package was
located.
(From yocto-docs rev: 8d3f7613f32f1ce91c9d53e2db3c36448abb5a82)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index cecfc95..93ac31c 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -839,7 +839,7 @@ so that there are some definite steps on how to do this. I need more detail her </note> <para> - Now that you know where to locate the work directory, you can use a + Now that you know where to locate the directory that has the temporary source code, you can use a Quilt or Git workflow to make your edits, test the changes, and preserve the changes in the form of patches. </para> @@ -864,10 +864,10 @@ so that there are some definite steps on how to do this. I need more detail her Yocto Project build directory. See the "<link linkend='finding-the-temporary-source-code'>Finding the Temporary Source Code</link>" - section to learn how to locate the work directory for a + section to learn how to locate the directory that has the temporary source code for a particular package.</para></listitem> <listitem><para><emphasis>Change Your Working Directory:</emphasis> - You need to be in the work directory that has the source code. + You need to be in the directory that has the temporary source code. That directory is defined by the <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#var-S'>S</ulink> variable.</para></listitem> @@ -960,10 +960,10 @@ so that there are some definite steps on how to do this. I need more detail her Yocto Project build directory. See the "<link linkend='finding-the-temporary-source-code'>Finding the Temporary Source Code</link>" - section to learn how to locate the work directory for a + section to learn how to locate the directory that has the temporary source code for a particular package.</para></listitem> <listitem><para><emphasis>Change Your Working Directory:</emphasis> - You need to be in the work directory. + You need to be in the directory that has the temporary source code. That directory is defined by the <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#var-S'>S</ulink> variable.</para></listitem> |
