docs/code-provenance: Fix formatting of *-by tags
Applying both ``code`` and **bold** formatting doesn't have the intended outcome, instead Sphinx emits the backticks into the HTML. Use only **bold** formatting to fix the HTML output. Signed-off-by: J. Neuschäfer <j.neuschaefer@9elements.com> Reviewed-by: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Link: https://lore.kernel.org/qemu-devel/20260520-prov-v1-1-7a58af334b9c@9elements.com Signed-off-by: Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
J. Neuschäfer committed
May 20, 2026 at 13:25 UTC
2f127af408e1b4675662f9b8a0c3606f6565a1a7
1 file changed
+5
-5
docs/devel/code-provenance.rst
+5
-5
@@ -99,13 +99,13 @@ Other commit tags
99
While the ``Signed-off-by`` tag is mandatory, there are a number of other tags
100
that are commonly used during QEMU development:
101
102
- * **``Reviewed-by``**: when a QEMU community member reviews a patch on the
102
+ * **Reviewed-by**: when a QEMU community member reviews a patch on the
103
mailing list, if they consider the patch acceptable, they should send an
104
email reply containing a ``Reviewed-by`` tag. Subsystem maintainers who
105
review a patch should add this even if they are also adding their
106
``Signed-off-by`` to the same commit.
107
108
- * **``Acked-by``**: when a QEMU subsystem maintainer approves a patch that
108
+ * **Acked-by**: when a QEMU subsystem maintainer approves a patch that
109
touches their subsystem, but intends to allow a different maintainer to
110
queue it and send a pull request, they would send a mail containing a
111
``Acked-by`` tag. Where a patch touches multiple subsystems, ``Acked-by``
@@ -113,18 +113,18 @@ that are commonly used during QEMU development:
113
maintainer wants to indicate they have done a full review they should use
114
a ``Reviewed-by`` tag.
115
116
- * **``Tested-by``**: when a QEMU community member has functionally tested the
116
+ * **Tested-by**: when a QEMU community member has functionally tested the
117
behaviour of the patch in some manner, they should send an email reply
118
containing a ``Tested-by`` tag.
119
120
- * **``Reported-by``**: when a QEMU community member reports a problem via the
120
+ * **Reported-by**: when a QEMU community member reports a problem via the
121
mailing list, or some other informal channel that is not the issue tracker,
122
it is good practice to credit them by including a ``Reported-by`` tag on
123
any patch fixing the issue. When the problem is reported via the GitLab
124
issue tracker, however, it is sufficient to just include a link to the
125
issue.
126
127
- * **``Suggested-by``**: when a reviewer or other 3rd party makes non-trivial
127
+ * **Suggested-by**: when a reviewer or other 3rd party makes non-trivial
128
suggestions for how to change a patch, it is good practice to credit them
129
by including a ``Suggested-by`` tag.
130