r600/sfn: Fix mapping for f32tof64 and f64tof32

[mesa.git] / docs / submittingpatches.html

diff --git a/docs/submittingpatches.html b/docs/submittingpatches.html
index 0f8bcb3284e11edb29816a414b396a32f1197971..fb614a790b6a0debbe6cf766af3c0b9513b987f9 100644 (file)
--- a/docs/submittingpatches.html
+++ b/docs/submittingpatches.html
@@ -76,7 +76,7 @@ platform.
 <li>If a patch addresses an issue in gitlab, use the Closes: tag
 For example:
 <pre>
-Closes: https://gitlab.freedesktop.org/mesa/mesa/issues/1
+Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/1
 </pre>
 <p>Prefer the full url to just <code>Closes: #1</code>, since the url makes it
 easier to get to the bug page from <code>git log</code></p>
@@ -215,7 +215,7 @@ Patches are submitted to the Mesa project via a
 
 <p>
   To participate in code review, you can monitor the GitLab Mesa
- <a href="https://gitlab.freedesktop.org/mesa/mesa/merge_requests">Merge
+ <a href="https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests">Merge
   Requests</a> page, and/or register for notifications in your gitlab
   settings.
 </p>
@@ -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