{"thread":{"id":"62275","subject":"[PATCH] docs: fix the `maintain-git` links in `technical/platform-support`","startedAt":"2024-10-07T21:49:28Z","lastAt":"2024-10-07T21:49:28Z","messageCount":1,"participants":["Johannes Schindelin via GitGitGadget"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"504366","messageId":"pull.1812.git.1728337764963.gitgitgadget@gmail.com","threadId":"62275","inReplyTo":null,"subject":"[PATCH] docs: fix the `maintain-git` links in `technical/platform-support`","fromName":"Johannes Schindelin via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2024-10-07T21:49:24Z","receivedAt":"2024-10-07T21:49:28Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"From: Johannes Schindelin <johannes.schindelin@gmx.de>\n\nThese links should point to `.html` files, not to `.txt` ones.\n\nCompare also to 4945f046c7f (api docs: link to html version of\napi-trace2, 2022-09-16).\n\nSigned-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>\n---\n    docs: fix the maintain-git links in technical/platform-support\n    \n    Noticed while deploying to git-scm.com\n    [https://github.com/git/git-scm.com/actions/runs/11219313103/job/31184984303].\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-1812%2Fdscho%2Ffix-maintain-git-links-v1\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1812/dscho/fix-maintain-git-links-v1\nPull-Request: https://github.com/gitgitgadget/git/pull/1812\n\n Documentation/technical/platform-support.txt | 4 ++--\n 1 file changed, 2 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/technical/platform-support.txt b/Documentation/technical/platform-support.txt\nindex a227c363d78..0a2fb28d627 100644\n--- a/Documentation/technical/platform-support.txt\n+++ b/Documentation/technical/platform-support.txt\n@@ -49,7 +49,7 @@ will be fixed in a later release:\n   notice problems before they are considered \"done with review\"; whereas\n   watching `master` means the stable branch could break for your platform, but\n   you have a decent chance of avoiding a tagged release breaking you. See \"The\n-  Policy\" in link:../howto/maintain-git.txt[\"How to maintain Git\"] for an\n+  Policy\" in link:../howto/maintain-git.html[\"How to maintain Git\"] for an\n   overview of which branches are used in the Git project, and how.\n \n * The bug report should include information about what platform you are using.\n@@ -125,7 +125,7 @@ Compatible on `next`\n \n To avoid reactive debugging and fixing when changes hit a release or stable, you\n can aim to ensure `next` always works for your platform. (See \"The Policy\" in\n-link:../howto/maintain-git.txt[\"How to maintain Git\"] for an overview of how\n+link:../howto/maintain-git.html[\"How to maintain Git\"] for an overview of how\n `next` is used in the Git project.) To do that:\n \n * You should add a runner for your platform to the GitHub Actions or GitLab CI\n\nbase-commit: 777489f9e09c8d0dd6b12f9d90de6376330577a2\n-- \ngitgitgadget\n"}]}