docs: make it clear that the tags needs to be in the commit message

Some people have been putting them only in the MR description, which
isn't picked up by our tools. (Note that doing both doesn't hurt.)

Signed-off-by: Eric Engestrom <eric@engestrom.ch>
Reviewed-by: Eric Anholt <eric@anholt.net>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5378>

diff --git a/docs/submittingpatches.rst b/docs/submittingpatches.rst
index 1556226ddec2be993bbb8802e5c83ab5f55982cb..984c0aa318610e53b76ca3fc6d7609a2c83d2258 100644 (file)
--- a/docs/submittingpatches.rst
+++ b/docs/submittingpatches.rst
@@ -64,7 +64,7 @@ Patch formatting
    something else.
 
 -  If a patch addresses a issue introduced with earlier commit, that
-   should be noted in the patch comment. For example:
+   should be noted in the commit message. For example:
 
    ::
 
@@ -254,9 +254,9 @@ Nominating a commit for a stable branch
 There are several ways to nominate a patch for inclusion in the stable
 branch and release. In order or preference:
 
-- By adding the ``Fixes:`` tag as described above, if you are fixing
+- By adding the ``Fixes:`` tag in the commit message as described above, if you are fixing
   a specific commit.
-- By adding the ``Cc: mesa-stable`` tag as described below.
+- By adding the ``Cc: mesa-stable`` tag in the commit message as described below.
 - By submitting a merge request against the ``staging/year.quarter``
   branch on gitlab.