Module: Mesa Branch: main Commit: ebc2af4e95e54021f860462f13f3f1a5a1a3d10b URL: http://cgit.freedesktop.org/mesa/mesa/commit/?id=ebc2af4e95e54021f860462f13f3f1a5a1a3d10b
Author: Eric Engestrom <[email protected]> Date: Thu Dec 28 10:42:16 2023 +0000 docs/backport-mr: fix invalid nested formatting Sphinx doesn't support that, so it renders verbatim. Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/26855> --- docs/submittingpatches.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/submittingpatches.rst b/docs/submittingpatches.rst index 57b880f9546..8c1c88e3ff0 100644 --- a/docs/submittingpatches.rst +++ b/docs/submittingpatches.rst @@ -393,7 +393,7 @@ For patches that either need to be nominated after they've landed in main, or that are known ahead of time to not not apply cleanly to a stable branch (such as due to a rename), using a GitLab MR is most appropriate. The MR should be based on and target the -``staging/**year.quarter**`` branch, not on the ``year.quarter`` branch, +``staging/year.quarter`` branch, not on the ``year.quarter`` branch, per the stable branch policy. Assigning the MR to release maintainer for said branch or mentioning them is helpful, but not required.
