aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRobert P. J. Day <rpjday@crashcourse.ca>2021-03-22 06:52:52 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-03-22 18:09:43 +0000
commit4a4d55c41806815c32add32863a05351a6df30f7 (patch)
tree2d9ec89a64811ec29b2661cb24535eb0cb7ff751
parent5e4e9acd323b5ebc3a14c07384f6cf8f8a272066 (diff)
downloadbitbake-4a4d55c41806815c32add32863a05351a6df30f7.tar.gz
doc: fix glossary link for BB_INVALIDCONF variable
Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--doc/bitbake-user-manual/bitbake-user-manual-metadata.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
index dcf664ebf..d4190c26e 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
@@ -1580,7 +1580,7 @@ might have an interest in viewing:
events when each of the workers parse the base configuration or if
the server changes configuration and reparses. Any given datastore
only has one such event executed against it, however. If
- ```BB_INVALIDCONF`` <#>`__ is set in the datastore by the event
+ :term:`BB_INVALIDCONF` is set in the datastore by the event
handler, the configuration is reparsed and a new event triggered,
allowing the metadata to update configuration.