Skip to content

Commit

Permalink
docs: fix the maintain-git links in technical/platform-support
Browse files Browse the repository at this point in the history
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 <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
dscho authored and gitster committed Oct 7, 2024
1 parent 777489f commit 4154ed4
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Documentation/technical/platform-support.txt
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down Expand Up @@ -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
Expand Down

0 comments on commit 4154ed4

Please sign in to comment.