From d4603d56c7137789a508b056cd585bef2ac9db45 Mon Sep 17 00:00:00 2001 From: "Robert P. J. Day" Date: Mon, 22 Mar 2021 06:52:52 -0400 Subject: bitbake: doc: fix glossary link for BB_INVALIDCONF variable (Bitbake rev: 4a4d55c41806815c32add32863a05351a6df30f7) Signed-off-by: Robert P. J. Day Signed-off-by: Richard Purdie --- bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'bitbake/doc') diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst index dcf664ebf4..d4190c26ee 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst +++ b/bitbake/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. -- cgit v1.2.3-54-g00ecf