[Mesa-dev] [PATCH 3/4] docs/submittingpatches.html: remove version tag for nominations

Nicolai Hähnle nhaehnle at gmail.com
Wed Feb 15 12:33:42 UTC 2017

On 13.02.2017 20:23, Emil Velikov wrote:
> From: Emil Velikov <emil.veliko at collabora.com>
> The version tag used to nominate has bitten even experienced mesa
> developers. Not to mention that it deviates from the one used in the
> kernel leading to further confusion.
> Simplify things and omit it all together.
> Signed-off-by: Emil Velcro <emil.velikov at collabora.com>

LOL. How did that happen? :)

I do like the change, thanks. In the rare case where a patch might apply 
to an older branch textually but cause problems, we can always state 
that in the commit message. What do you think?


> ---
> Another option would be to align it with the kernel one, but that could
> bring even further confusion.
> I'll gladly welcome any input on the topic.
> ---
>  docs/submittingpatches.html | 10 ++--------
>  1 file changed, 2 insertions(+), 8 deletions(-)
> diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html
> index 69835af6eb..564ad731b2 100644
> --- a/docs/submittingpatches.html
> +++ b/docs/submittingpatches.html
> @@ -233,17 +233,11 @@ Here are some examples of such a note:
>  </p>
>  <ul>
>    <li>CC: <mesa-stable at lists.freedesktop.org></li>
> -  <li>CC: "9.2 10.0" <mesa-stable at lists.freedesktop.org></li>
> -  <li>CC: "10.0" <mesa-stable at lists.freedesktop.org></li>
>  </ul>
>  Simply adding the CC to the mesa-stable list address is adequate to nominate
> -the commit for the most-recently-created stable branch. It is only necessary
> -to specify a specific branch name, (such as "9.2 10.0" or "10.0" in the
> -examples above), if you want to nominate the commit for an older stable
> -branch. And, as in these examples, you can nominate the commit for the older
> -branch in addition to the more recent branch, or nominate the commit
> -exclusively for the older branch.
> +the commit for all the active stable branches. If the commit is not applicable
> +for said branch the stable-release manager will reply stating so.
>  This "CC" syntax for patch nomination will cause patches to automatically be
>  copied to the mesa-stable@ mailing list when you use "git send-email" to send

More information about the mesa-dev mailing list