summaryrefslogtreecommitdiff
path: root/docs/submittingpatches.html
diff options
context:
space:
mode:
authorEmil Velikov <emil.velikov@collabora.com>2016-12-05 16:11:21 +0000
committerEmil Velikov <emil.l.velikov@gmail.com>2016-12-09 17:37:30 +0000
commit0715ba4be6ff4633ba9623cec53861474ce1a528 (patch)
tree4dbf47e92bc691ba542067c4f770e8e145d34b47 /docs/submittingpatches.html
parent26541a1fcc1fbb1e4aa25e79225bbe43d50d600d (diff)
docs: document how to (self-) reject stable patches
Document what has been the unofficial way to self-reject stable patches. Namely: drop the mesa-stable tag and push the commit. Signed-off-by: Emil Velikov <emil.velikov@collabora.com> Reviewed-by: Nanley Chery <nanley.g.chery@intel.com>
Diffstat (limited to 'docs/submittingpatches.html')
-rw-r--r--docs/submittingpatches.html7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html
index d1ca68d06c..141cec2758 100644
--- a/docs/submittingpatches.html
+++ b/docs/submittingpatches.html
@@ -249,6 +249,13 @@ copied to the mesa-stable@ mailing list when you use "git send-email" to send
patches to the mesa-dev@ mailing list. If you prefer using --suppress-cc that
won't have any effect negative effect on the patch nomination.
+<p>
+Note: by removing the tag [as the commit is pushed] the patch is
+<strong>explicitly</strong> rejected from inclusion in the stable branch(es).
+<br>
+Thus, drop the line <strong>only</strong> if you want to cancel the nomination.
+</p>
+
<h2 id="criteria">Criteria for accepting patches to the stable branch</h2>
Mesa has a designated release manager for each stable branch, and the release