Suggested-by: Emil Velikov <[email protected]> Signed-off-by: Eric Engestrom <[email protected]> --- docs/submittingpatches.html | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+)
diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index ba09aa4ad7329327e760..34c375cdaa44fe4fc197 100644 --- a/docs/submittingpatches.html +++ b/docs/submittingpatches.html @@ -23,6 +23,7 @@ <h1>Submitting patches</h1> <li><a href="#testing">Testing Patches</a> <li><a href="#mailing">Mailing Patches</a> <li><a href="#reviewing">Reviewing Patches</a> +<li><a href="#pushing">Pushing Patches</a> <li><a href="#nominations">Nominating a commit for a stable branch</a> <li><a href="#criteria">Criteria for accepting patches to the stable branch</a> <li><a href="#backports">Sending backports for the stable branch</a> @@ -230,6 +231,31 @@ <h2 id="reviewing">Reviewing Patches</h2> </p> +<h2 id="pushing">Pushing patches</h2> + +<p> +Patches should remain available for review for a certain period, +depending on the severity of what they change. +Patches that fix serious regressions (fails to build, most of piglit/CTS +fails, etc.) are likely to be pushed on a shorter notice. +</p> + +<p> +Reviewed patches are pushed to the <a href="repository.html">upstream repository</a> +by developers with <a href="repository.html#developer">commit access</a>. +If you do not have access, clearly state so (normally after the +<code>---</code> line) as part of the patch submission, and a reviewer +will push it for you. +</p> + +<p> +If you notice your patch hasn't been pushed after having been reviewed, +don't hesitate to poke developers (preferably by replying to the review +email). Emails do fall through the cracks sometimes, nothing personal +about it :) +</p> + + <h2 id="nominations">Nominating a commit for a stable branch</h2> <p> -- Cheers, Eric _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
