Mesa (master): docs: make it clear that the tags needs to be in the commit message

[GitLab Mirror]

Module: Mesa
Branch: master
Commit: 7488d491072cbd98e3bfc6d39b2ca10504572e72
URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=7488d491072cbd98e3bfc6d39b2ca10504572e72

Author: Eric Engestrom <eric at engestrom.ch>
Date:   Sun Jun  7 17:57:52 2020 +0200

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 at engestrom.ch>
Reviewed-by: Eric Anholt <eric at anholt.net>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5378>

---

 docs/submittingpatches.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/submittingpatches.rst b/docs/submittingpatches.rst
index 1556226ddec..984c0aa3186 100644
--- 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.