Skip to content

Commit 99e5b8e

Browse files
committed
docs: fix the maintain-git links in technical/platform-support
These links should point to `.html` files, not to `.txt` ones. Compare also to 4945f04 (api docs: link to html version of api-trace2, 2022-09-16). Signed-off-by: Johannes Schindelin <[email protected]>
1 parent 777489f commit 99e5b8e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

Documentation/technical/platform-support.txt

+2-2
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ will be fixed in a later release:
4949
notice problems before they are considered "done with review"; whereas
5050
watching `master` means the stable branch could break for your platform, but
5151
you have a decent chance of avoiding a tagged release breaking you. See "The
52-
Policy" in link:../howto/maintain-git.txt["How to maintain Git"] for an
52+
Policy" in link:../howto/maintain-git.html["How to maintain Git"] for an
5353
overview of which branches are used in the Git project, and how.
5454

5555
* The bug report should include information about what platform you are using.
@@ -125,7 +125,7 @@ Compatible on `next`
125125

126126
To avoid reactive debugging and fixing when changes hit a release or stable, you
127127
can aim to ensure `next` always works for your platform. (See "The Policy" in
128-
link:../howto/maintain-git.txt["How to maintain Git"] for an overview of how
128+
link:../howto/maintain-git.html["How to maintain Git"] for an overview of how
129129
`next` is used in the Git project.) To do that:
130130

131131
* You should add a runner for your platform to the GitHub Actions or GitLab CI

0 commit comments

Comments
 (0)