Commit f1fe74af authored by Erik Faye-Lund 's avatar Erik Faye-Lund 💬 Committed by Marge Bot
Browse files

docs: update internal references

Part-of: <mesa/mesa!4630>
parent ea91f476
......@@ -44,5 +44,5 @@ before running the game.
Viewperf
--------
See the `Viewperf issues <viewperf.html>`__ page for a detailed list of
See the `Viewperf issues <viewperf.rst>`__ page for a detailed list of
Viewperf issues.
......@@ -39,7 +39,7 @@ Contents
--------
Proceed to the `compilation and installation
instructions <install.html>`__.
instructions <install.rst>`__.
Demos, GLUT, and GLU
--------------------
......
......@@ -28,7 +28,7 @@ Build EGL
-D gallium-drivers=...
The main library and OpenGL is enabled by default. The first two
options above enables `OpenGL ES 1.x and 2.x <opengles.html>`__. The
options above enables `OpenGL ES 1.x and 2.x <opengles.rst>`__. The
last two options enables the listed classic and Gallium drivers
respectively.
......
......@@ -163,14 +163,14 @@ Core Mesa environment variables
variable is set), or else within ``.cache/mesa_shader_cache`` within
the user's home directory.
``MESA_GLSL``
`shading language compiler options <shading.html#envvars>`__
`shading language compiler options <shading.rst#envvars>`__
``MESA_NO_MINMAX_CACHE``
when set, the minmax index cache is globally disabled.
``MESA_SHADER_CAPTURE_PATH``
see `Capturing Shaders <shading.html#capture>`__
see `Capturing Shaders <shading.rst#capture>`__
``MESA_SHADER_DUMP_PATH`` and ``MESA_SHADER_READ_PATH``
see `Experimenting with Shader
Replacements <shading.html#replacement>`__
Replacements <shading.rst#replacement>`__
``MESA_VK_VERSION_OVERRIDE``
changes the Vulkan physical device version as returned in
``VkPhysicalDeviceProperties::apiVersion``.
......@@ -202,7 +202,7 @@ Mesa Xlib driver environment variables
--------------------------------------
The following are only applicable to the Mesa Xlib software driver. See
the `Xlib software driver page <xlibdriver.html>`__ for details.
the `Xlib software driver page <xlibdriver.rst>`__ for details.
``MESA_RGB_VISUAL``
specifies the X visual and depth for RGB mode
......@@ -342,7 +342,7 @@ EGL environment variables
-------------------------
Mesa EGL supports different sets of environment variables. See the `Mesa
EGL <egl.html>`__ page for the details.
EGL <egl.rst>`__ page for the details.
Gallium environment variables
-----------------------------
......
......@@ -85,7 +85,7 @@ drivers within the DRI (Direct Rendering Infrastructure):
This wasn't easy in the past. Now, the DRI drivers are included in the
Mesa tree and can be compiled separately from the X server. Just follow
the Mesa `compilation instructions <install.html>`__.
the Mesa `compilation instructions <install.rst>`__.
1.6 Are there other open-source implementations of OpenGL?
----------------------------------------------------------
......@@ -262,7 +262,7 @@ problem.
4.1 How can I contribute?
~~~~~~~~~~~~~~~~~~~~~~~~~
First, join the `mesa-dev mailing list <lists.html>`__. That's where
First, join the `mesa-dev mailing list <lists.rst>`__. That's where
Mesa development is discussed.
The `OpenGL Specification <https://www.opengl.org/documentation>`__ is
......
......@@ -102,7 +102,7 @@ On windows you can also use the visual studio backend
cd builddir
msbuild mesa.sln /m
Please read the `detailed meson instructions <meson.html>`__ for more
Please read the `detailed meson instructions <meson.rst>`__ for more
information
3. Building with SCons (Windows/Linux)
......
......@@ -5,7 +5,7 @@ Mesa implements OpenGL ES 1.1 and OpenGL ES 2.0. More information about
OpenGL ES can be found at https://www.khronos.org/opengles/.
OpenGL ES depends on a working EGL implementation. Please refer to `Mesa
EGL <egl.html>`__ for more information about EGL.
EGL <egl.rst>`__ for more information about EGL.
Build the Libraries
-------------------
......
......@@ -17,9 +17,9 @@ used, best practices and other details, the member in charge of the next
feature release will be in constant rotation.
The way the release schedule works is explained
`here <releasing.html#schedule>`__.
`here <releasing.rst#schedule>`__.
Take a look `here <submittingpatches.html#criteria>`__ if you'd like to
Take a look `here <submittingpatches.rst#criteria>`__ if you'd like to
nominate a patch in the next stable release.
Calendar
......
......@@ -27,7 +27,7 @@ Release schedule
Releases should happen on Wednesdays. Delays can occur although those
should be kept to a minimum.
See our `calendar <release-calendar.html>`__ for information about how
See our `calendar <release-calendar.rst>`__ for information about how
the release schedule is planned, and the date and other details for
individual releases.
......@@ -58,7 +58,7 @@ Stable releases
This also involves that, as a final release may be delayed due to the
need of additional candidates to solve some blocking regression(s), the
release manager might have to update the
`calendar <release-calendar.html>`__ with additional bug fix releases of
`calendar <release-calendar.rst>`__ with additional bug fix releases of
the current stable branch.
.. _pickntest:
......@@ -67,7 +67,7 @@ Cherry-picking and testing
--------------------------
Commits nominated for the active branch are picked as based on the
`criteria <submittingpatches.html#criteria>`__ as described in the same
`criteria <submittingpatches.rst#criteria>`__ as described in the same
section.
Nominations happen via special tags in the commit messages, and via
......@@ -174,7 +174,7 @@ to stabilisation and bugfixing.
should be tackled already.
Check if the version number is going to remain as, alternatively
``git mv docs/relnotes/{current,new}.html`` as appropriate.
``git mv docs/relnotes/{current,new}.rst`` as appropriate.
To setup the branchpoint:
......@@ -290,7 +290,7 @@ respectively.
Add the sha256sums to the release notes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Edit docs/relnotes/X.Y.Z.html to add the sha256sum as available in the
Edit docs/relnotes/X.Y.Z.rst to add the sha256sum as available in the
mesa-X.Y.Z.announce template. Commit this change.
Back on mesa master, add the new release notes into the tree
......@@ -310,7 +310,7 @@ Then run the
./bin/post_version.py X.Y.Z
, where X.Y.Z is the version you just made. This will updated
docs/relnotes.html, docs/index.html, and docs/release-calendar.html. It
docs/relnotes.rst, docs/index.rst, and docs/release-calendar.rst. It
will then generate a git commit automatically. Check that everything
looks correct and push:
......@@ -329,7 +329,7 @@ series, if that is the case.
Update gitlab issues
--------------------
Parse through the bug reports as listed in the docs/relnotes/X.Y.Z.html
Parse through the bug reports as listed in the docs/relnotes/X.Y.Z.rst
document. If there's outstanding action, close the bug referencing the
commit ID which addresses the bug and mention the Mesa version that has
the fix.
......
This diff is collapsed.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment