{"thread":{"id":"66900","subject":"[PATCH] doc: fix AsciiDoc syntax","startedAt":"2026-11-20T17:12:32Z","lastAt":"2026-11-21T00:41:27Z","messageCount":8,"participants":["Ophir Bleicher via GitGitGadget","Ben Knoble","Junio C Hamano","Ophir Bleicher"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"558977","messageId":"pull.2496.git.git.1795194752259.gitgitgadget@gmail.com","threadId":"66900","inReplyTo":null,"subject":"[PATCH] doc: fix AsciiDoc syntax","fromName":"Ophir Bleicher via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2026-11-20T17:12:32Z","receivedAt":"2026-11-20T17:12:32Z","isPatch":true,"sender":{"key":"name:Ophir Bleicher","avatar":null},"body":"From: Ophir Bleicher <ophirble@gmail.com>\n\nThe Documentation/MyFirstContribution.adoc file accidentally used\nMarkdown syntax for a link:\n\n[here](https://gitgitgadget.github.io/#...)\n\nFixed it to use AsciiDoc:\n\nhttps://gitgitgadget.github.io/#...[here]\n\nSigned-off-by: Ophir Bleicher <ophirble@gmail.com>\n---\n    doc: fix AsciiDoc syntax\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2496%2FOphirBleicher%2Fpatch-3-v1\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2496/OphirBleicher/patch-3-v1\nPull-Request: https://github.com/git/git/pull/2496\n\n Documentation/MyFirstContribution.adoc | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\nindex c58253fd54..3b531b24fa 100644\n--- a/Documentation/MyFirstContribution.adoc\n+++ b/Documentation/MyFirstContribution.adoc\n@@ -931,7 +931,7 @@ either with the \"New pull request\" button or the convenient \"Compare & pull\n request\" button that may appear with the name of your newly pushed branch.\n \n The differences between using `gitgitgadget/git` and `git/git` as your base can\n-be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n+be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[here]\n \n Review the PR's title and description, as they're used by GitGitGadget\n respectively as the subject and body of the cover letter for your change. Refer\n\nbase-commit: f7de81456940dd6f3274e461149bba12965de609\n-- \ngitgitgadget\n\n"},{"id":"558980","messageId":"93127462-BCFD-4086-B19D-4B640F515140@gmail.com","threadId":"66900","inReplyTo":"pull.2496.git.git.1795194752259.gitgitgadget@gmail.com","subject":"Re: [PATCH] doc: fix AsciiDoc syntax","fromName":"Ben Knoble","fromEmail":"ben.knoble@gmail.com","sentAt":"2026-11-20T17:54:24Z","receivedAt":"2026-11-20T17:54:24Z","isPatch":true,"sender":{"key":"ben.knoble@gmail.com","avatar":"https://avatars.githubusercontent.com/u/22802209?v=4"},"body":"\n> Le 20 nov. 2026 à 12:31, Ophir Bleicher via GitGitGadget <gitgitgadget@gmail.com> a écrit :\n> \n> ﻿From: Ophir Bleicher <ophirble@gmail.com>\n> \n> The Documentation/MyFirstContribution.adoc file accidentally used\n> Markdown syntax for a link:\n> \n> [here](https://gitgitgadget.github.io/#...)\n> \n> Fixed it to use AsciiDoc:\n> \n> https://gitgitgadget.github.io/#...[here]\n\nGood catch.\n\nWhile we’re at it, « here » is generally discouraged as link text.\nIt’s not particularly accessible for screen-readers, for example.\n\n> Signed-off-by: Ophir Bleicher <ophirble@gmail.com>\n> ---\n>    doc: fix AsciiDoc syntax\n> \n> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2496%2FOphirBleicher%2Fpatch-3-v1\n> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2496/OphirBleicher/patch-3-v1\n> Pull-Request: https://github.com/git/git/pull/2496\n> \n> Documentation/MyFirstContribution.adoc | 2 +-\n> 1 file changed, 1 insertion(+), 1 deletion(-)\n> \n> diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n> index c58253fd54..3b531b24fa 100644\n> --- a/Documentation/MyFirstContribution.adoc\n> +++ b/Documentation/MyFirstContribution.adoc\n> @@ -931,7 +931,7 @@ either with the \"New pull request\" button or the convenient \"Compare & pull\n> request\" button that may appear with the name of your newly pushed branch.\n> \n> The differences between using `gitgitgadget/git` and `git/git` as your base can\n> -be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n> +be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[here]\n\nSo perhaps we could reword this to something like\n\n    Further [differences between …] are described online.\n\nwith the brackets marking the link text?\n\n> Review the PR's title and description, as they're used by GitGitGadget\n> respectively as the subject and body of the cover letter for your change. Refer\n> \n> base-commit: f7de81456940dd6f3274e461149bba12965de609\n> --\n> gitgitgadget\n> \n\n"},{"id":"558983","messageId":"xmqqh5hbqst1.fsf@gitster.g","threadId":"66900","inReplyTo":"93127462-BCFD-4086-B19D-4B640F515140@gmail.com","subject":"Re: [PATCH] doc: fix AsciiDoc syntax","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-11-20T18:08:42Z","receivedAt":"2026-11-20T18:08:42Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ben Knoble <ben.knoble@gmail.com> writes:\n\n>> Fixed it to use AsciiDoc:\n>> \n>> https://gitgitgadget.github.io/#...[here]\n>\n> Good catch.\n>\n> While we’re at it, « here » is generally discouraged as link text.\n> It’s not particularly accessible for screen-readers, for example.\n\nI also thought that it was a funny but understandable mistake we\nmade, given how prevalent Markdown is these days, but didn't think\nof the need to improve the link text.\n\nGreat suggestion.\n\n>> The differences between using `gitgitgadget/git` and `git/git` as your base can\n>> -be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n>> +be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[here]\n>\n> So perhaps we could reword this to something like\n>\n>     Further [differences between …] are described online.\n>\n> with the brackets marking the link text?\n\nSounds good.\n\nThanks.\n\n"},{"id":"558986","messageId":"pull.2496.v2.git.git.1795199746309.gitgitgadget@gmail.com","threadId":"66900","inReplyTo":"pull.2496.git.git.1795194752259.gitgitgadget@gmail.com","subject":"[PATCH v2] doc: fix AsciiDoc syntax","fromName":"Ophir Bleicher via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2026-11-20T18:35:46Z","receivedAt":"2026-11-20T18:35:46Z","isPatch":true,"sender":{"key":"name:Ophir Bleicher","avatar":null},"body":"From: Ophir Bleicher <ophirble@gmail.com>\n\nThe Documentation/MyFirstContribution.adoc file accidentally used\nMarkdown syntax for a link:\n\n[here](https://gitgitgadget.github.io/#...)\n\nFixed it to use AsciiDoc:\n\nhttps://gitgitgadget.github.io/#...[here]\n\nSigned-off-by: Ophir Bleicher <ophirble@gmail.com>\n---\n    doc: fix AsciiDoc syntax\n    \n    Difference from v1:\n    \n     * Change link text\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2496%2FOphirBleicher%2Fpatch-3-v2\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2496/OphirBleicher/patch-3-v2\nPull-Request: https://github.com/git/git/pull/2496\n\nRange-diff vs v1:\n\n 1:  748ac69283 ! 1:  cf26060e59 doc: fix AsciiDoc syntax\n     @@ Documentation/MyFirstContribution.adoc: either with the \"New pull request\" butto\n       \n       The differences between using `gitgitgadget/git` and `git/git` as your base can\n      -be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n     -+be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[here]\n     ++be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[on GitGitGadget's official documentation.]\n       \n       Review the PR's title and description, as they're used by GitGitGadget\n       respectively as the subject and body of the cover letter for your change. Refer\n\n\n Documentation/MyFirstContribution.adoc | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\nindex c58253fd54..73dab5f7c9 100644\n--- a/Documentation/MyFirstContribution.adoc\n+++ b/Documentation/MyFirstContribution.adoc\n@@ -931,7 +931,7 @@ either with the \"New pull request\" button or the convenient \"Compare & pull\n request\" button that may appear with the name of your newly pushed branch.\n \n The differences between using `gitgitgadget/git` and `git/git` as your base can\n-be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n+be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[on GitGitGadget's official documentation.]\n \n Review the PR's title and description, as they're used by GitGitGadget\n respectively as the subject and body of the cover letter for your change. Refer\n\nbase-commit: f7de81456940dd6f3274e461149bba12965de609\n-- \ngitgitgadget\n\n"},{"id":"558990","messageId":"xmqqtslbpbpa.fsf@gitster.g","threadId":"66900","inReplyTo":"pull.2496.v2.git.git.1795199746309.gitgitgadget@gmail.com","subject":"Re: [PATCH v2] doc: fix AsciiDoc syntax","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-11-20T19:03:29Z","receivedAt":"2026-11-20T19:03:29Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Ophir Bleicher via GitGitGadget\" <gitgitgadget@gmail.com> writes:\n\n> From: Ophir Bleicher <ophirble@gmail.com>\n>\n> The Documentation/MyFirstContribution.adoc file accidentally used\n> Markdown syntax for a link:\n>\n> [here](https://gitgitgadget.github.io/#...)\n>\n> Fixed it to use AsciiDoc:\n>\n> https://gitgitgadget.github.io/#...[here]\n>\n> Signed-off-by: Ophir Bleicher <ophirble@gmail.com>\n> ---\n\nThe exact same tense and mood suggestion applies to this commit\nmessage, too.  \"uses\" and \"Fix\".  I can locally tweak them while\nqueuing, so no need to resend if you are OK with it.\n\n>     doc: fix AsciiDoc syntax\n>     \n>     Difference from v1:\n>     \n>      * Change link text\n>\n> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2496%2FOphirBleicher%2Fpatch-3-v2\n> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2496/OphirBleicher/patch-3-v2\n> Pull-Request: https://github.com/git/git/pull/2496\n>\n> Range-diff vs v1:\n>\n>  1:  748ac69283 ! 1:  cf26060e59 doc: fix AsciiDoc syntax\n>      @@ Documentation/MyFirstContribution.adoc: either with the \"New pull request\" butto\n>        \n>        The differences between using `gitgitgadget/git` and `git/git` as your base can\n>       -be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n>      -+be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[here]\n>      ++be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[on GitGitGadget's official documentation.]\n>        \n>        Review the PR's title and description, as they're used by GitGitGadget\n>        respectively as the subject and body of the cover letter for your change. Refer\n>\n>\n>  Documentation/MyFirstContribution.adoc | 2 +-\n>  1 file changed, 1 insertion(+), 1 deletion(-)\n>\n> diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n> index c58253fd54..73dab5f7c9 100644\n> --- a/Documentation/MyFirstContribution.adoc\n> +++ b/Documentation/MyFirstContribution.adoc\n> @@ -931,7 +931,7 @@ either with the \"New pull request\" button or the convenient \"Compare & pull\n>  request\" button that may appear with the name of your newly pushed branch.\n>  \n>  The differences between using `gitgitgadget/git` and `git/git` as your base can\n> -be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n> +be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[on GitGitGadget's official documentation.]\n>  \n>  Review the PR's title and description, as they're used by GitGitGadget\n>  respectively as the subject and body of the cover letter for your change. Refer\n>\n> base-commit: f7de81456940dd6f3274e461149bba12965de609\n\n"},{"id":"558992","messageId":"072A2362-2FCF-4DC0-8460-86B63498226E@gmail.com","threadId":"66900","inReplyTo":"xmqqtslbpbpa.fsf@gitster.g","subject":"Re: [PATCH v2] doc: fix AsciiDoc syntax","fromName":"Ophir Bleicher","fromEmail":"ophirble@gmail.com","sentAt":"2026-11-20T19:25:16Z","receivedAt":"2026-11-20T19:25:16Z","isPatch":true,"sender":{"key":"ophirble@gmail.com","avatar":null},"body":"OK, thank you!\n\n> On 20 Nov 2026, at 21:03, Junio C Hamano <gitster@pobox.com> wrote:\n> \n> \"Ophir Bleicher via GitGitGadget\" <gitgitgadget@gmail.com> writes:\n> \n>> From: Ophir Bleicher <ophirble@gmail.com>\n>> \n>> The Documentation/MyFirstContribution.adoc file accidentally used\n>> Markdown syntax for a link:\n>> \n>> [here](https://gitgitgadget.github.io/#...)\n>> \n>> Fixed it to use AsciiDoc:\n>> \n>> https://gitgitgadget.github.io/#...[here]\n>> \n>> Signed-off-by: Ophir Bleicher <ophirble@gmail.com>\n>> ---\n> \n> The exact same tense and mood suggestion applies to this commit\n> message, too.  \"uses\" and \"Fix\".  I can locally tweak them while\n> queuing, so no need to resend if you are OK with it.\n> \n>>    doc: fix AsciiDoc syntax\n>> \n>>    Difference from v1:\n>> \n>>     * Change link text\n>> \n>> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2496%2FOphirBleicher%2Fpatch-3-v2\n>> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2496/OphirBleicher/patch-3-v2\n>> Pull-Request: https://github.com/git/git/pull/2496\n>> \n>> Range-diff vs v1:\n>> \n>> 1:  748ac69283 ! 1:  cf26060e59 doc: fix AsciiDoc syntax\n>>     @@ Documentation/MyFirstContribution.adoc: either with the \"New pull request\" butto\n>> \n>>       The differences between using `gitgitgadget/git` and `git/git` as your base can\n>>      -be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n>>     -+be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[here]\n>>     ++be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[on GitGitGadget's official documentation.]\n>> \n>>       Review the PR's title and description, as they're used by GitGitGadget\n>>       respectively as the subject and body of the cover letter for your change. Refer\n>> \n>> \n>> Documentation/MyFirstContribution.adoc | 2 +-\n>> 1 file changed, 1 insertion(+), 1 deletion(-)\n>> \n>> diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n>> index c58253fd54..73dab5f7c9 100644\n>> --- a/Documentation/MyFirstContribution.adoc\n>> +++ b/Documentation/MyFirstContribution.adoc\n>> @@ -931,7 +931,7 @@ either with the \"New pull request\" button or the convenient \"Compare & pull\n>> request\" button that may appear with the name of your newly pushed branch.\n>> \n>> The differences between using `gitgitgadget/git` and `git/git` as your base can\n>> -be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n>> +be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[on GitGitGadget's official documentation.]\n>> \n>> Review the PR's title and description, as they're used by GitGitGadget\n>> respectively as the subject and body of the cover letter for your change. Refer\n>> \n>> base-commit: f7de81456940dd6f3274e461149bba12965de609\n\n\n\n"},{"id":"559011","messageId":"85D05F5D-111B-4A60-A923-B45FD514CADC@gmail.com","threadId":"66900","inReplyTo":"pull.2496.v2.git.git.1795199746309.gitgitgadget@gmail.com","subject":"Re: [PATCH v2] doc: fix AsciiDoc syntax","fromName":"Ben Knoble","fromEmail":"ben.knoble@gmail.com","sentAt":"2026-11-21T00:18:37Z","receivedAt":"2026-11-21T00:18:37Z","isPatch":true,"sender":{"key":"ben.knoble@gmail.com","avatar":"https://avatars.githubusercontent.com/u/22802209?v=4"},"body":"\n> Le 20 nov. 2026 à 13:37, Ophir Bleicher via GitGitGadget <gitgitgadget@gmail.com> a écrit :\n> \n> ﻿From: Ophir Bleicher <ophirble@gmail.com>\n> \n> The Documentation/MyFirstContribution.adoc file accidentally used\n> Markdown syntax for a link:\n> \n> [here](https://gitgitgadget.github.io/#...)\n> \n> Fixed it to use AsciiDoc:\n> \n> https://gitgitgadget.github.io/#...[here]\n> \n> Signed-off-by: Ophir Bleicher <ophirble@gmail.com>\n> ---\n>    doc: fix AsciiDoc syntax\n> \n>    Difference from v1:\n> \n>     * Change link text\n> \n> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2496%2FOphirBleicher%2Fpatch-3-v2\n> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2496/OphirBleicher/patch-3-v2\n> Pull-Request: https://github.com/git/git/pull/2496\n> \n> Range-diff vs v1:\n> \n> 1:  748ac69283 ! 1:  cf26060e59 doc: fix AsciiDoc syntax\n>     @@ Documentation/MyFirstContribution.adoc: either with the \"New pull request\" butto\n> \n>       The differences between using `gitgitgadget/git` and `git/git` as your base can\n>      -be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n>     -+be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[here]\n>     ++be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[on GitGitGadget's official documentation.]\n\nI’m happy with this link text, thanks.\n\n>       Review the PR's title and description, as they're used by GitGitGadget\n>       respectively as the subject and body of the cover letter for your change. Refer\n> \n> \n> Documentation/MyFirstContribution.adoc | 2 +-\n> 1 file changed, 1 insertion(+), 1 deletion(-)\n> \n> diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n> index c58253fd54..73dab5f7c9 100644\n> --- a/Documentation/MyFirstContribution.adoc\n> +++ b/Documentation/MyFirstContribution.adoc\n> @@ -931,7 +931,7 @@ either with the \"New pull request\" button or the convenient \"Compare & pull\n> request\" button that may appear with the name of your newly pushed branch.\n> \n> The differences between using `gitgitgadget/git` and `git/git` as your base can\n> -be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n> +be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[on GitGitGadget's official documentation.]\n> \n> Review the PR's title and description, as they're used by GitGitGadget\n> respectively as the subject and body of the cover letter for your change. Refer\n> \n> base-commit: f7de81456940dd6f3274e461149bba12965de609\n> --\n> gitgitgadget\n> \n\n"},{"id":"559013","messageId":"xmqqh5hbm2x4.fsf@gitster.g","threadId":"66900","inReplyTo":"85D05F5D-111B-4A60-A923-B45FD514CADC@gmail.com","subject":"Re: [PATCH v2] doc: fix AsciiDoc syntax","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-11-21T00:41:27Z","receivedAt":"2026-11-21T00:41:27Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ben Knoble <ben.knoble@gmail.com> writes:\n\n>>       The differences between using `gitgitgadget/git` and `git/git` as your base can\n>>      -be found [here](https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror)\n>>     -+be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[here]\n>>     ++be found https://gitgitgadget.github.io/#should-i-use-gitgitgadget-on-gitgitgadgets-git-fork-or-on-gits-github-mirror[on GitGitGadget's official documentation.]\n>\n> I’m happy with this link text, thanks.\n\nThanks for writing and reviewing.  Let me mark it as ready for\n'next', then.\n\n"}]}