docs: drop open-coded toc for articles
Sphinx already provides a proper table-of-contents, so we don't need to roll our own. Reviewed-by: Eric Engestrom <eric@engestrom.ch> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4630>
This commit is contained in:
parent
d6be994ef8
commit
14f2a81b6f
7 changed files with 0 additions and 120 deletions
|
|
@ -1,18 +1,6 @@
|
|||
Submitting Patches
|
||||
==================
|
||||
|
||||
- `Basic guidelines <#guidelines>`__
|
||||
- `Patch formatting <#formatting>`__
|
||||
- `Testing Patches <#testing>`__
|
||||
- `Submitting Patches <#submit>`__
|
||||
- `Reviewing Patches <#reviewing>`__
|
||||
- `Nominating a commit for a stable branch <#nominations>`__
|
||||
- `Criteria for accepting patches to the stable branch <#criteria>`__
|
||||
- `Sending backports for the stable branch <#backports>`__
|
||||
- `Git tips <#gittips>`__
|
||||
|
||||
.. _guidelines:
|
||||
|
||||
Basic guidelines
|
||||
----------------
|
||||
|
||||
|
|
@ -259,8 +247,6 @@ project. The submitter is expected to evaluate whether they have an
|
|||
appropriate amount of review feedback from people who also understand
|
||||
the code before merging their patches.
|
||||
|
||||
.. _nominations:
|
||||
|
||||
Nominating a commit for a stable branch
|
||||
---------------------------------------
|
||||
|
||||
|
|
@ -281,8 +267,6 @@ nomination request.
|
|||
The current patch status can be observed in the `staging
|
||||
branch <releasing.html#stagingbranch>`__.
|
||||
|
||||
.. _thetag:
|
||||
|
||||
The stable tag
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
|
|
@ -375,8 +359,6 @@ staging/year.quarter branch, not on the year.quarter branch, per the
|
|||
stable branch policy. Assigning the MR to release maintainer for said
|
||||
branch or mentioning them is helpful, but not required.
|
||||
|
||||
.. _gittips:
|
||||
|
||||
Git tips
|
||||
--------
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue