X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Fsubmittingpatches.rst;h=712adfc5c9b799e2cd1e2026049dbdb155542c35;hb=eb02b311234b71b155496681f294954f3de61823;hp=98398d972ab63d74a53ef82798446d90abe747d7;hpb=b1c16e52514fd9e66d3ac118f1ec32a83cbc5f2a;p=mesa.git

diff --git a/docs/submittingpatches.rst b/docs/submittingpatches.rst
index 98398d972ab..712adfc5c9b 100644
--- a/docs/submittingpatches.rst
+++ b/docs/submittingpatches.rst
@@ -112,7 +112,7 @@ The ``Fixes:`` tag
 If a patch addresses a issue introduced with earlier commit, that
 should be noted in the commit message. For example::
 
-    Fixes: d7b3707c612 "util/disk_cache: use stat() to check if entry is a directory"
+    Fixes: d7b3707c612 ("util/disk_cache: use stat() to check if entry is a directory")
 
 You can produce those fixes lines by running this command once::
 
@@ -134,6 +134,8 @@ to automatically, so you don't need to figure it out.
 Alternatively, you may use a "CC:" tag. Here are some examples of such a
 note::
 
+    Cc: mesa-stable
+    Cc: 20.0 <mesa-stable>
     CC: 20.0 19.3 <mesa-stable>
 
 Using the CC tag **should** include the stable branches you want to