summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml7
1 files changed, 4 insertions, 3 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index e456d540a0..b42a09bf2b 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -1716,8 +1716,9 @@
<para>
If you're working on a recipe that pulls from an external Source Code Manager (SCM), it
- is possible to have the OpenEmbedded build system notice new changes added to the
- SCM and then build the package that depends on them using the latest version.
+ is possible to have the OpenEmbedded build system notice new recipe changes added to the
+ SCM and then build the resulting package that depends on the new recipes by using the latest
+ versions.
This only works for SCMs from which it is possible to get a sensible revision number for changes.
Currently, you can do this with Apache Subversion (SVN), Git, and Bazaar (BZR) repositories.
</para>
@@ -1730,7 +1731,7 @@
SRCREV_pn-&lt;PN&gt; = "${AUTOREV}"
</literallayout>
where <filename>PN</filename>
- is the name of the package for which you want to enable automatic source
+ is the name of the recipe for which you want to enable automatic source
revision updating.
</para>
</section>