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>
Acked-by: Joe Hacker <jhacker@foo.com>
- If sending later revision of a patch, add all the tags - ack, r-b,
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:
feedback if the patch has already been reviewed.
.. _testing:
There are three ways to nominate a patch for inclusion in the stable
branch and release.
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.
- By adding the fixes: tag as described below.
- By submitting a merge request against the "staging/year.quarter"
branch on gitlab.
- 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
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