diff mbox series

docs: fix the `maintain-git` links in `technical/platform-support`

Message ID pull.1812.git.1728337764963.gitgitgadget@gmail.com (mailing list archive)
State Accepted
Commit 4154ed41085933e7a433e796b431b5466debfa4f
Headers show
Series docs: fix the `maintain-git` links in `technical/platform-support` | expand

Commit Message

Johannes Schindelin Oct. 7, 2024, 9:49 p.m. UTC 
From: Johannes Schindelin <johannes.schindelin@gmx.de>

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>
---
    docs: fix the maintain-git links in technical/platform-support
    
    Noticed while deploying to git-scm.com
    [https://github.com/git/git-scm.com/actions/runs/11219313103/job/31184984303].

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1812%2Fdscho%2Ffix-maintain-git-links-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1812/dscho/fix-maintain-git-links-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1812

 Documentation/technical/platform-support.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)


base-commit: 777489f9e09c8d0dd6b12f9d90de6376330577a2
diff mbox series

Patch

diff --git a/Documentation/technical/platform-support.txt b/Documentation/technical/platform-support.txt
index a227c363d78..0a2fb28d627 100644
--- a/Documentation/technical/platform-support.txt
+++ b/Documentation/technical/platform-support.txt
@@ -49,7 +49,7 @@  will be fixed in a later release:
   notice problems before they are considered "done with review"; whereas
   watching `master` means the stable branch could break for your platform, but
   you have a decent chance of avoiding a tagged release breaking you. See "The
-  Policy" in link:../howto/maintain-git.txt["How to maintain Git"] for an
+  Policy" in link:../howto/maintain-git.html["How to maintain Git"] for an
   overview of which branches are used in the Git project, and how.
 
 * The bug report should include information about what platform you are using.
@@ -125,7 +125,7 @@  Compatible on `next`
 
 To avoid reactive debugging and fixing when changes hit a release or stable, you
 can aim to ensure `next` always works for your platform. (See "The Policy" in
-link:../howto/maintain-git.txt["How to maintain Git"] for an overview of how
+link:../howto/maintain-git.html["How to maintain Git"] for an overview of how
 `next` is used in the Git project.) To do that:
 
 * You should add a runner for your platform to the GitHub Actions or GitLab CI