docs: fix the `maintain-git` links in `technical/platform-support`
These links should point to `.html` files, not to `.txt` ones. Compare also to 4945f046c7f (api docs: link to html version of api-trace2, 2022-09-16). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Johannes Schindelin committed
Oct 7, 2024 at 21:49 UTC
4154ed41085933e7a433e796b431b5466debfa4f
1 file changed
+2
-2
Documentation/technical/platform-support.txt
+2
-2
@@ -49,7 +49,7 @@ will be fixed in a later release:
49
notice problems before they are considered "done with review"; whereas
50
watching `master` means the stable branch could break for your platform, but
51
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
53
overview of which branches are used in the Git project, and how.
54
55
* The bug report should include information about what platform you are using.
@@ -125,7 +125,7 @@ Compatible on `next`
125
126
To avoid reactive debugging and fixing when changes hit a release or stable, you
127
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
129
`next` is used in the Git project.) To do that:
130
131
* You should add a runner for your platform to the GitHub Actions or GitLab CI