OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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>
This commit is contained in:
Eric Engestrom
2020-06-07 17:57:52 +02:00
committed by Marge Bot
parent 731465192a
commit 7488d49107
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/submittingpatches.rst
View File

@@ -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.