docs: stop considering `Cc: mesa-stable` as an email address

Our tools haven't needed more than this ^ for a while, and the historical
reasons this used to be an email address don't matter anymore.

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 94f5b7426ab5b93e89d2978a7ac2468361cd2f2e..611d5f56fa1ae20c0625bc9a8a104d2841ce16f7 100644 (file)
--- a/docs/submittingpatches.rst
+++ b/docs/submittingpatches.rst
@@ -116,7 +116,7 @@ Patch formatting
       Acked-by: Joe Hacker <jhacker@foo.com>
 
 -  If sending later revision of a patch, add all the tags - ack, r-b,
-   Cc: mesa-stable and/or other. This provides reviewers with quick
+   ``Cc: mesa-stable`` and/or other. This provides reviewers with quick
    feedback if the patch has already been reviewed.
 
 .. _testing:
@@ -253,7 +253,7 @@ Nominating a commit for a stable branch
 There are three ways to nominate a patch for inclusion in the stable
 branch and release.
 
--  By adding the Cc: mesa-stable@ tag as described below.
+- By adding the ``Cc: mesa-stable`` tag as described below.
 -  By adding the fixes: tag as described below.
 -  By submitting a merge request against the "staging/year.quarter"
    branch on gitlab.
@@ -284,7 +284,7 @@ note:
 
 ::
 
-   CC: 20.0 19.3 <mesa-stable@lists.freedesktop.org>
+   CC: 20.0 19.3 <mesa-stable>
 
 Using the CC tag **should** include the stable branches you want to
 nominate the patch to. If you do not provide any version it is nominated