From 9e4248b20695672bd0fe8668cea290d2aecd36bd Mon Sep 17 00:00:00 2001 From: Emil Velikov Date: Mon, 13 Feb 2017 19:23:40 +0000 Subject: [PATCH] docs/submittingpatches.html: remove version tag for nominations MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit 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 Velikov Reviewed-by: Nicolai Hähnle --- docs/submittingpatches.html | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index 69835af6ebb..564ad731b24 100644 --- a/docs/submittingpatches.html +++ b/docs/submittingpatches.html @@ -233,17 +233,11 @@ Here are some examples of such a note:

  • CC: <mesa-stable@lists.freedesktop.org>
    • -
  • CC: "9.2 10.0" <mesa-stable@lists.freedesktop.org>
    • -
  • CC: "10.0" <mesa-stable@lists.freedesktop.org>
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 -- 2.30.2