On 11/16, Emil Velikov wrote:
From: Emil Velikov <emil.veli...@collabora.com>Currently things are a bit buried within the text, making it harder to find out. Move at the top and be clear what is _not_ a good idea. We had some people consistently using the "bad" way and then being unhappy that their patches were missed/delayed. Cc: Marek Olšák <marek.ol...@amd.com> Signed-off-by: Emil Velikov <emil.veli...@collabora.com> --- docs/submittingpatches.html | 30 ++++++++++++++++++++---------- 1 file changed, 20 insertions(+), 10 deletions(-) diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index 77b870a..07777ab 100644 --- a/docs/submittingpatches.html +++ b/docs/submittingpatches.html @@ -184,6 +184,24 @@ as the issues are resolved first. <h2 id="nominations">Nominating a commit for a stable branch</h2> <p> +There are three ways to nominate patch for inclusion of the stable branch and +release. +</p> +<ul> +<li> By adding the Cc: mesa-stable@ tag as described below. +<li> Sending the commit ID (as seen in master branch) to the mesa-stable@ mailing list. +<li> Forwarding the patch from the mesa-dev@ mailing list. +</li> +</ul> +<p> +Note: sending [re]sending patch identical to one on mesa-dev@ or one that
"sending [re]sending"? Just "resending" seems sufficient.
signature.asc
Description: Digital signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
