diff options
author | Emil Velikov <[email protected]> | 2016-12-05 16:11:21 +0000 |
---|---|---|
committer | Emil Velikov <[email protected]> | 2016-12-09 17:37:30 +0000 |
commit | 0715ba4be6ff4633ba9623cec53861474ce1a528 (patch) | |
tree | 4dbf47e92bc691ba542067c4f770e8e145d34b47 | |
parent | 26541a1fcc1fbb1e4aa25e79225bbe43d50d600d (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 <[email protected]>
Reviewed-by: Nanley Chery <[email protected]>
-rw-r--r-- | docs/submittingpatches.html | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index d1ca68d06c1..141cec27581 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 |