diff options
| author | Erik Faye-Lund <[email protected]> | 2020-04-20 23:08:14 +0200 |
|---|---|---|
| committer | Marge Bot <[email protected]> | 2020-04-21 09:49:22 +0000 |
| commit | d29fea77b9182915c1689634ff2376ac3c8fc21b (patch) | |
| tree | 01dfa7a82cd15f9c63063b659a920aa6734999a1 | |
| parent | 56f174d14eb4bdac07ae34b0538cfcc217d7eca5 (diff) | |
docs: remove outdated sentence
The releasing documentation no longer contains this step, so this seems
out of date. The anchor for this link is also removed, making it point
nowhere.
Fixes: d4cb9ef8260 ("docs: Update release notes with current process")
Reviewed-by: Eric Engestrom <[email protected]>
Reviewed-by: Dylan Baker <[email protected]>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4654>
| -rw-r--r-- | docs/submittingpatches.html | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html index 0f8bcb3284e..15674291d08 100644 --- a/docs/submittingpatches.html +++ b/docs/submittingpatches.html @@ -373,9 +373,6 @@ If the patch complies with the rules it will be manager will reply to the patch in question stating why the patch has been rejected or would request a backport. -A summary of all the picked/rejected patches will be presented in the -<a href="releasing.html#prerelease">pre-release</a> announcement. - The stable-release manager may at times need to force-push changes to the stable branches, for example, to drop a previously-picked patch that was later identified as causing a regression). These force-pushes may cause changes to |