summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Engestrom <eric@engestrom.ch>2020-06-07 17:31:01 +0200
committerMarge Bot <eric+marge@anholt.net>2020-06-19 19:51:53 +0000
commitfdebba27709884878aa7c828cc72f208303e038f (patch)
treead6f559f863e6430901333a470dbfc802df60eae
parentb1a98a1107ad70b1a6864dd38f33beebe689fec7 (diff)
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>
-rw-r--r--docs/submittingpatches.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/submittingpatches.rst b/docs/submittingpatches.rst
index 94f5b7426ab..611d5f56fa1 100644
--- 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