aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTaylor Blau <me@ttaylorr.com>2024-10-15 16:56:43 -0400
committerTaylor Blau <me@ttaylorr.com>2024-10-15 16:56:43 -0400
commit8a5545b949287eb09597d1c37130539f50a2e09a (patch)
treed51e53af723713bac27cb4b60831be6115a453e2
parentf004467b042d735a2fe8bd5706b053b04b1aec65 (diff)
parent4154ed41085933e7a433e796b431b5466debfa4f (diff)
downloadgit-8a5545b949287eb09597d1c37130539f50a2e09a.tar.gz
Merge branch 'js/doc-platform-support-link-fix'
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