diff options
author | Trevor Woerner <twoerner@gmail.com> | 2025-05-23 21:49:02 -0400 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2025-05-26 13:02:49 +0100 |
commit | be2eaa114b9654f303a409bd4e59e9ed36315e0e (patch) | |
tree | d9d671a97f46773332d29d2ec679916ea73c3887 /documentation/toaster-manual/reference.rst | |
parent | fe721fe5748eba8e6f27ba2b3c74efc79878b827 (diff) | |
download | poky-be2eaa114b9654f303a409bd4e59e9ed36315e0e.tar.gz |
sphinx-lint: unbalanced inline literal markup
Fix as many instances of unbalanced-inline-literals-delimiters as reported
by 'make sphinx-lint' as possible. Sphinx and/or its linter seem to get
tripped up randomly when references contain links to a heading which
contain literals enclosed in double-back-tics; especially in the cases
where a heading either contains multiple literals or when the literal is
not at the end of the heading. Not all of them can be "fixed" to pass both
building and linting.
(From yocto-docs rev: 3460177c46d360b0f2f852cdab23f21bd4ec6d5a)
Signed-off-by: Trevor Woerner <twoerner@gmail.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/toaster-manual/reference.rst')
-rw-r--r-- | documentation/toaster-manual/reference.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/toaster-manual/reference.rst b/documentation/toaster-manual/reference.rst index 755b895cee..3050b5d0f5 100644 --- a/documentation/toaster-manual/reference.rst +++ b/documentation/toaster-manual/reference.rst | |||
@@ -546,7 +546,7 @@ database. | |||
546 | 546 | ||
547 | You need to run the ``buildslist`` command first to identify existing | 547 | You need to run the ``buildslist`` command first to identify existing |
548 | builds in the database before using the | 548 | builds in the database before using the |
549 | :ref:`toaster-manual/reference:\`\`builddelete\`\`` command. Here is an | 549 | :ref:`toaster-manual/reference:``builddelete``` command. Here is an |
550 | example that assumes default repository and :term:`Build Directory` names: | 550 | example that assumes default repository and :term:`Build Directory` names: |
551 | 551 | ||
552 | .. code-block:: shell | 552 | .. code-block:: shell |
@@ -555,7 +555,7 @@ example that assumes default repository and :term:`Build Directory` names: | |||
555 | $ python ../bitbake/lib/toaster/manage.py buildslist | 555 | $ python ../bitbake/lib/toaster/manage.py buildslist |
556 | 556 | ||
557 | If your Toaster database had only one build, the above | 557 | If your Toaster database had only one build, the above |
558 | :ref:`toaster-manual/reference:\`\`buildslist\`\`` | 558 | :ref:`toaster-manual/reference:``buildslist``` |
559 | command would return something like the following:: | 559 | command would return something like the following:: |
560 | 560 | ||
561 | 1: qemux86 poky core-image-minimal | 561 | 1: qemux86 poky core-image-minimal |
@@ -576,7 +576,7 @@ the database. | |||
576 | 576 | ||
577 | Prior to running the ``builddelete`` command, you need to get the ID | 577 | Prior to running the ``builddelete`` command, you need to get the ID |
578 | associated with builds by using the | 578 | associated with builds by using the |
579 | :ref:`toaster-manual/reference:\`\`buildslist\`\`` command. | 579 | :ref:`toaster-manual/reference:``buildslist``` command. |
580 | 580 | ||
581 | ``perf`` | 581 | ``perf`` |
582 | -------- | 582 | -------- |