aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2024-11-25 12:29:41 +0900
committerJunio C Hamano <gitster@pobox.com>2024-11-25 12:29:41 +0900
commitf675674ced080c0065ebebc7f69a2f6a0889e36d (patch)
treeb13f3af3ec84fa8cea8d886b1f6bcad3775b971a
parente52276d340bc58590a6ba6468f74d4b6db06ce86 (diff)
parent4154ed41085933e7a433e796b431b5466debfa4f (diff)
downloadgit-f675674ced080c0065ebebc7f69a2f6a0889e36d.tar.gz
Merge branch 'js/doc-platform-support-link-fix' into maint-2.47
Docfix. * js/doc-platform-support-link-fix: docs: fix the `maintain-git` links in `technical/platform-support`
-rw-r--r--Documentation/technical/platform-support.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/technical/platform-support.txt b/Documentation/technical/platform-support.txt
index a227c363d7..0a2fb28d62 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