Lines Matching refs:stable

103    ``Fixes:``, ``Cc: mesa-stable`` and/or other) to the commit messages.
123 The stable tag
126 If you want a commit to be applied to a stable branch, you should add an
137     Cc: mesa-stable
138     Cc: 20.0 <mesa-stable>
139     CC: 20.0 19.3 <mesa-stable>
141 Using the CC tag **should** include the stable branches you want to
143 to all active stable branches.
273 Nominating a commit for a stable branch
276 There are several ways to nominate a patch for inclusion in the stable
281 - By adding the ``Cc: mesa-stable`` tag in the commit message as described above.
285 Please **DO NOT** send patches to mesa-stable@lists.freedesktop.org, it
296 Criteria for accepting patches to the stable branch
299 Mesa has a designated release manager for each stable branch, and the
303 accepted and which are not. The stable-release manager is also given
338 been rejected or would request a backport. The stable-release manager
339 may at times need to force-push changes to the stable branches, for
342 from the stable branch if developers push things directly. Consider
347 Sending backports for the stable branch
350 By default merge conflicts are resolved by the stable-release manager.
357 stable branch (such as due to a rename), using a GitLab MR is most
360 stable branch policy. Assigning the MR to release maintainer for said