{"thread":{"id":"63992","subject":"[PATCH] doc:clarify which remotes can be used when contributing","startedAt":"2025-08-19T19:14:45Z","lastAt":"2025-08-26T06:50:26Z","messageCount":11,"participants":["Daniele Sassoli via GitGitGadget","Junio C Hamano","Daniele Sassoli","Elijah Newren"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"524465","messageId":"pull.2034.git.git.1755630882418.gitgitgadget@gmail.com","threadId":"63992","inReplyTo":null,"subject":"[PATCH] doc:clarify which remotes can be used when contributing","fromName":"Daniele Sassoli via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2025-08-19T19:14:42Z","receivedAt":"2025-08-19T19:14:45Z","isPatch":true,"sender":{"key":"danielesassoli@gmail.com","avatar":"https://avatars.githubusercontent.com/u/4007741?v=4"},"body":"From: Daniele Sassoli <danielesassoli@gmail.com>\n\nThe docs mostly point to using git/git as one's remote, however, when it\ncomes to Sending a PR to GitGitGadget section, the reader is told to use\ngitgitgadget/git, with no mention of git/git, potentially leading to\nsome confusion.\n\nClarify that both gitgitgadget/git and git/git can be used, albeit with\nsome differences.\n\nSigned-off-by: Daniele Sassoli <danielesassoli@gmail.com>\n---\n    doc:clarify which remotes can be used when contributing\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2034%2FDanieleSassoli%2Fclarify-remote-to-use-v1\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2034/DanieleSassoli/clarify-remote-to-use-v1\nPull-Request: https://github.com/git/git/pull/2034\n\n Documentation/MyFirstContribution.adoc | 8 +++++++-\n 1 file changed, 7 insertions(+), 1 deletion(-)\n\ndiff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\nindex aca7212cfe2..d014c5c36e1 100644\n--- a/Documentation/MyFirstContribution.adoc\n+++ b/Documentation/MyFirstContribution.adoc\n@@ -908,10 +908,16 @@ Now you should be able to go and check out your newly created branch on GitHub.\n === Sending a PR to GitGitGadget\n \n In order to have your code tested and formatted for review, you need to start by\n-opening a Pull Request against `gitgitgadget/git`. Head to\n+opening a Pull Request against either `gitgitgadget/git` or `git/git`, depending\n+on which mirror you initially cloned from. Head to\n https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n request\" button or the convenient \"Compare & pull request\" button that may\n appear with the name of your newly pushed branch.\n+If you're using https://github.com/git/git as your remote, you will need to\n+open the pull-request from your fork, selecting `git/git` as base.\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 \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: c44beea485f0f2feaf460e2ac87fdd5608d63cf0\n-- \ngitgitgadget\n"},{"id":"524489","messageId":"xmqqms7vc8mo.fsf@gitster.g","threadId":"63992","inReplyTo":"pull.2034.git.git.1755630882418.gitgitgadget@gmail.com","subject":"Re: [PATCH] doc:clarify which remotes can be used when contributing","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-19T21:19:11Z","receivedAt":"2025-08-19T21:19:13Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Daniele Sassoli via GitGitGadget\" <gitgitgadget@gmail.com> writes:\n>  https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n>  request\" button or the convenient \"Compare & pull request\" button that may\n>  appear with the name of your newly pushed branch.\n> +If you're using https://github.com/git/git as your remote, you will need to\n> +open the pull-request from your fork, selecting `git/git` as base.\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\nLooking at the table, there is no advantage to use git/git at all.\n\nInstead of telling them that they can use either (with reduced\ncapabilities if you pick one of them instead of the other), wouldn't\nit be easier for the user if this section taught them how to switch\ntheir fork that they originally created out of git/git to be based\non gitgitgadget/git instead?  Something along the lines of\n\n    ... If you originally forked from https://github.com/git/git/,\n    you can easily correct it by running (you only need to do this\n    once):\n\n    $ git remote set-url origin https://github.com/gitgitgadget/git/\n    $ git fetch --prune origin\n\n    A pull request at https://github.com/gitgitgadget/git/ can be\n    opened once you do so.\n\nbut you'd need to validate the procedure, as I didn't try it myself.\n\nThanks.\n"},{"id":"524526","messageId":"363ac6d1-8444-4d48-a66b-51ea139f4e87@gmail.com","threadId":"63992","inReplyTo":"xmqqms7vc8mo.fsf@gitster.g","subject":"Re: [PATCH] doc:clarify which remotes can be used when contributing","fromName":"Daniele Sassoli","fromEmail":"danielesassoli@gmail.com","sentAt":"2025-08-20T14:07:36Z","receivedAt":"2025-08-20T14:07:39Z","isPatch":true,"sender":{"key":"danielesassoli@gmail.com","avatar":"https://avatars.githubusercontent.com/u/4007741?v=4"},"body":"\nOn 19/08/2025 22:19, Junio C Hamano wrote:\n> \"Daniele Sassoli via GitGitGadget\" <gitgitgadget@gmail.com> writes:\n>>   https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n>>   request\" button or the convenient \"Compare & pull request\" button that may\n>>   appear with the name of your newly pushed branch.\n>> +If you're using https://github.com/git/git as your remote, you will need to\n>> +open the pull-request from your fork, selecting `git/git` as base.\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> Looking at the table, there is no advantage to use git/git at all.\n>\n> Instead of telling them that they can use either (with reduced\n> capabilities if you pick one of them instead of the other), wouldn't\n> it be easier for the user if this section taught them how to switch\n> their fork that they originally created out of git/git to be based\n\nMost of the document, including the \"Getting Started\" section, points to cloning\nfrom git/git. It's only when it comes to the gitgitgadget section that we\nmention gitgitgadget/git.\n\nIt's true that there are no advantages of using git/git over gitgitgadget/git,\nbut I would argue that the disadvantages are quite minor and definitely don't\nimpact someone at their first contribution?\n\nAs we've told the reader so far to use git/git, I don't see why we should tell\nhim to change his remote for potentially no benefit. If we're saying that\ngitgitgadget should be used only on gitgitgadget/git, then we should restructure\nthe document to point to that from the beginning, no?\n\nPS. please note it's my first time replying on the mailing list directly,\napologies if I did something wrong, like wrong posting style or wrong people in\ncc.\n\n> on gitgitgadget/git instead?  Something along the lines of\n>\n>      ... If you originally forked from https://github.com/git/git/,\n>      you can easily correct it by running (you only need to do this\n>      once):\n>\n>      $ git remote set-url origin https://github.com/gitgitgadget/git/\n>      $ git fetch --prune origin\n>\n>      A pull request at https://github.com/gitgitgadget/git/ can be\n>      opened once you do so.\n>\n> but you'd need to validate the procedure, as I didn't try it myself.\n>\n> Thanks.\n"},{"id":"524573","messageId":"xmqqbjo98zjh.fsf@gitster.g","threadId":"63992","inReplyTo":"363ac6d1-8444-4d48-a66b-51ea139f4e87@gmail.com","subject":"Re: [PATCH] doc:clarify which remotes can be used when contributing","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-20T21:16:02Z","receivedAt":"2025-08-20T21:16:04Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Daniele Sassoli <danielesassoli@gmail.com> writes:\n\n> On 19/08/2025 22:19, Junio C Hamano wrote:\n>> \"Daniele Sassoli via GitGitGadget\" <gitgitgadget@gmail.com> writes:\n>>>   https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n>>>   request\" button or the convenient \"Compare & pull request\" button that may\n>>>   appear with the name of your newly pushed branch.\n>>> +If you're using https://github.com/git/git as your remote, you will need to\n>>> +open the pull-request from your fork, selecting `git/git` as base.\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>> Looking at the table, there is no advantage to use git/git at all.\n>\n> Most of the document, including the \"Getting Started\" section, points to cloning\n> from git/git. It's only when it comes to the gitgitgadget section that we\n> mention gitgitgadget/git.\n>\n> It's true that there are no advantages of using git/git over gitgitgadget/git,\n> but I would argue that the disadvantages are quite minor and definitely don't\n> impact someone at their first contribution?\n\nEven the disabled things may be rather advanced features, wouldn't\nit still impact them for them to stay to be on git/git?\n\nThose started from git/git have to learn what different things they\nneed to do to use GGG by reading this extra piece of documentation,\nand then if they plan to keep using GGG, they will have to do this\nextra thing each and every time until the end of time (since your\npreference is not to teach switching to GGG/git from git/git).\n\nI have no strong opinions as I wouldn't be the one who is doing\nsomething extra every time, but I'd rather see our new contributors\nhaving to spend less time to get their work published and more time\nto polish their work into reviewable state.\n\n"},{"id":"524706","messageId":"acbb5f69-98bf-4eab-99ea-08b3155ce9e2@gmail.com","threadId":"63992","inReplyTo":"xmqqbjo98zjh.fsf@gitster.g","subject":"Re: [PATCH] doc:clarify which remotes can be used when contributing","fromName":"Daniele Sassoli","fromEmail":"danielesassoli@gmail.com","sentAt":"2025-08-22T09:14:20Z","receivedAt":"2025-08-22T09:14:23Z","isPatch":true,"sender":{"key":"danielesassoli@gmail.com","avatar":"https://avatars.githubusercontent.com/u/4007741?v=4"},"body":"\nOn 20/08/2025 22:16, Junio C Hamano wrote:\n> Daniele Sassoli <danielesassoli@gmail.com> writes:\n>\n>> On 19/08/2025 22:19, Junio C Hamano wrote:\n>>> \"Daniele Sassoli via GitGitGadget\" <gitgitgadget@gmail.com> writes:\n>>>>    https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n>>>>    request\" button or the convenient \"Compare & pull request\" button that may\n>>>>    appear with the name of your newly pushed branch.\n>>>> +If you're using https://github.com/git/git as your remote, you will need to\n>>>> +open the pull-request from your fork, selecting `git/git` as base.\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>>> Looking at the table, there is no advantage to use git/git at all.\n>> Most of the document, including the \"Getting Started\" section, points to cloning\n>> from git/git. It's only when it comes to the gitgitgadget section that we\n>> mention gitgitgadget/git.\n>>\n>> It's true that there are no advantages of using git/git over gitgitgadget/git,\n>> but I would argue that the disadvantages are quite minor and definitely don't\n>> impact someone at their first contribution?\n\nFirst of all, thanks for taking the time to review this series, really\nappreciate it.\n\n> Even the disabled things may be rather advanced features, wouldn't\n> it still impact them for them to stay to be on git/git?\n>\n> Those started from git/git have to learn what different things they\n> need to do to use GGG by reading this extra piece of documentation,\n> and then if they plan to keep using GGG, they will have to do this\n> extra thing each and every time until the end of time (since your\n> preference is not to teach switching to GGG/git from git/git).\n\nI think for someone's first contribution, the most straightforward thing to do\nis simply to stick with what they have setup so far. If someone finds themselves\ndoing this more than once, I would imagine they know what they're doing and are\nnot beginners, so can figure out to switch the remote themselves.\n\n>\n> I have no strong opinions as I wouldn't be the one who is doing\n> something extra every time, but I'd rather see our new contributors\n> having to spend less time to get their work published and more time\n> to polish their work into reviewable state.\n\nWe're trying to achieve the same outcome, which is why I'm trying to have the\nreader follow the path of least resistance in getting their patch to the mailing\nlist. If they then find themselves contributing regularly and realise they need\nthe more advanced features of gitgitgadget on a regular basis, I'm sure they'll\nfigure to switch the remote themselves.\n\n>\n"},{"id":"524721","messageId":"xmqq349jxmsr.fsf@gitster.g","threadId":"63992","inReplyTo":"acbb5f69-98bf-4eab-99ea-08b3155ce9e2@gmail.com","subject":"Re: [PATCH] doc:clarify which remotes can be used when contributing","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-22T17:56:36Z","receivedAt":"2025-08-22T17:56:38Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Daniele Sassoli <danielesassoli@gmail.com> writes:\n\n> Subject: Re: [PATCH] doc:clarify which remotes can be used when contributing\n\nA space is missing before \"clarify\".\n\n>> Those started from git/git have to learn what different things they\n>> need to do to use GGG by reading this extra piece of documentation,\n>> and then if they plan to keep using GGG, they will have to do this\n>> extra thing each and every time until the end of time (since your\n>> preference is not to teach switching to GGG/git from git/git).\n>\n> I think for someone's first contribution, the most straightforward thing to do\n> is simply to stick with what they have setup so far. If someone finds themselves\n> doing this more than once, I would imagine they know what they're doing and are\n> not beginners, so can figure out to switch the remote themselves.\n> ...\n> We're trying to achieve the same outcome, which is why I'm trying to have the\n> reader follow the path of least resistance in getting their patch to the mailing\n> list. If they then find themselves contributing regularly and realise they need\n> the more advanced features of gitgitgadget on a regular basis, I'm sure they'll\n> figure to switch the remote themselves.\n\nHaving been in this project for longer than some people, I strongly\nsuspect that \"they'll figure to switch\" will never happen.  Even\nwhen a solution they have (e.g. \"Here is how you work around to use\nGGG when you didn't start with GGG\") is more cumbersome than it has\nto be, people tend to stay there in a local minimum, not necessarily\nout of habit and laziness, but because they are not told that there\nare better ways.  When they do not know they need to \"figure to\nswitch\", they won't.\n\nHaving said that, as I said, I do not have strong opinions, so I'll\nlet other people to discuss and come to their own consensus ;-)\n\nThanks for writing a patch.\n"},{"id":"524726","messageId":"CABPp-BEVzNDurd1h+Jw905RO9bg16eDacqg_Ee7GD66Muj0fSg@mail.gmail.com","threadId":"63992","inReplyTo":"pull.2034.git.git.1755630882418.gitgitgadget@gmail.com","subject":"Re: [PATCH] doc:clarify which remotes can be used when contributing","fromName":"Elijah Newren","fromEmail":"newren@gmail.com","sentAt":"2025-08-22T18:45:46Z","receivedAt":"2025-08-22T18:45:58Z","isPatch":true,"sender":{"key":"newren@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5455730?v=4"},"body":"On Tue, Aug 19, 2025 at 12:14 PM Daniele Sassoli via GitGitGadget\n<gitgitgadget@gmail.com> wrote:\n>\n> From: Daniele Sassoli <danielesassoli@gmail.com>\n>\n> The docs mostly point to using git/git as one's remote, however, when it\n> comes to Sending a PR to GitGitGadget section, the reader is told to use\n> gitgitgadget/git, with no mention of git/git, potentially leading to\n> some confusion.\n>\n> Clarify that both gitgitgadget/git and git/git can be used, albeit with\n> some differences.\n>\n> Signed-off-by: Daniele Sassoli <danielesassoli@gmail.com>\n> ---\n>     doc:clarify which remotes can be used when contributing\n>\n> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2034%2FDanieleSassoli%2Fclarify-remote-to-use-v1\n> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2034/DanieleSassoli/clarify-remote-to-use-v1\n> Pull-Request: https://github.com/git/git/pull/2034\n>\n>  Documentation/MyFirstContribution.adoc | 8 +++++++-\n>  1 file changed, 7 insertions(+), 1 deletion(-)\n>\n> diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n> index aca7212cfe2..d014c5c36e1 100644\n> --- a/Documentation/MyFirstContribution.adoc\n> +++ b/Documentation/MyFirstContribution.adoc\n> @@ -908,10 +908,16 @@ Now you should be able to go and check out your newly created branch on GitHub.\n>  === Sending a PR to GitGitGadget\n>\n>  In order to have your code tested and formatted for review, you need to start by\n> -opening a Pull Request against `gitgitgadget/git`. Head to\n> +opening a Pull Request against either `gitgitgadget/git` or `git/git`, depending\n> +on which mirror you initially cloned from. Head to\n\nI think mentioning that opening a PR in either project is fine is\nhelpful...especially since the UI sometimes changes the target to\ngit/git when I wanted to open against gitgitgadget/git, and I don't\nnotice and I open yet another PR in the wrong place.  However, having\nit opened in the wrong place rarely makes any meaningful difference,\nso it would probably be helpful to let new users know that it's okay\nto open it in either place as you do here.\n\nHowever, where you cloned from doesn't matter when you open the pull\nrequest, so I'd strike the \", depending on which mirror you initially\ncloned from.\" part of this change.\n\n>  https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n>  request\" button or the convenient \"Compare & pull request\" button that may\n>  appear with the name of your newly pushed branch.\n> +If you're using https://github.com/git/git as your remote, you will need to\n> +open the pull-request from your fork, selecting `git/git` as base.\n\n...and I think we should strike these two sentences as well, or at\nleast reword them; your remote URL is immaterial.\n\n(Not only have I opened up against both gitgitgadget/git and git/git\nin the past, my clone URL wasn't necessarily either one of these.)\n\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\nI like this call out.\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: c44beea485f0f2feaf460e2ac87fdd5608d63cf0\n> --\n> gitgitgadget\n\nThanks for sending the patch in.\n"},{"id":"524773","messageId":"pull.2034.v2.git.git.1755940331248.gitgitgadget@gmail.com","threadId":"63992","inReplyTo":"pull.2034.git.git.1755630882418.gitgitgadget@gmail.com","subject":"[PATCH v2] doc:clarify which remotes can be used when contributing","fromName":"Daniele Sassoli via GitGitGadget","fromEmail":"gitgitgadget@gmail.com","sentAt":"2025-08-23T09:12:11Z","receivedAt":"2025-08-23T09:12:14Z","isPatch":true,"sender":{"key":"danielesassoli@gmail.com","avatar":"https://avatars.githubusercontent.com/u/4007741?v=4"},"body":"From: Daniele Sassoli <danielesassoli@gmail.com>\n\nThe docs mostly point to using git/git as one's remote, however, when it\ncomes to Sending a PR to GitGitGadget section, the reader is told to use\ngitgitgadget/git, with no mention of git/git, potentially leading to\nsome confusion.\n\nClarify that both gitgitgadget/git and git/git can be used, albeit with\nsome differences.\n\nSigned-off-by: Daniele Sassoli <danielesassoli@gmail.com>\n---\n    doc:clarify which remotes can be used when contributing\n    \n    cc: Elijah Newren newren@gmail.com\n\nPublished-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2034%2FDanieleSassoli%2Fclarify-remote-to-use-v2\nFetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2034/DanieleSassoli/clarify-remote-to-use-v2\nPull-Request: https://github.com/git/git/pull/2034\n\nRange-diff vs v1:\n\n 1:  850097696a4 ! 1:  b34070c03e3 doc:clarify which remotes can be used when contributing\n     @@ Documentation/MyFirstContribution.adoc: Now you should be able to go and check o\n       \n       In order to have your code tested and formatted for review, you need to start by\n      -opening a Pull Request against `gitgitgadget/git`. Head to\n     -+opening a Pull Request against either `gitgitgadget/git` or `git/git`, depending\n     -+on which mirror you initially cloned from. Head to\n     - https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n     - request\" button or the convenient \"Compare & pull request\" button that may\n     - appear with the name of your newly pushed branch.\n     -+If you're using https://github.com/git/git as your remote, you will need to\n     -+open the pull-request from your fork, selecting `git/git` as base.\n     +-https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n     +-request\" button or the convenient \"Compare & pull request\" button that may\n     +-appear with the name of your newly pushed branch.\n     ++opening a Pull Request against either `gitgitgadget/git` or `git/git`. Head to\n     ++https://github.com/gitgitgadget/git or https://github.com/git/git and open a PR\n     ++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\n\n Documentation/MyFirstContribution.adoc | 11 +++++++----\n 1 file changed, 7 insertions(+), 4 deletions(-)\n\ndiff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\nindex aca7212cfe2..bbb7b45bd4a 100644\n--- a/Documentation/MyFirstContribution.adoc\n+++ b/Documentation/MyFirstContribution.adoc\n@@ -908,10 +908,13 @@ Now you should be able to go and check out your newly created branch on GitHub.\n === Sending a PR to GitGitGadget\n \n In order to have your code tested and formatted for review, you need to start by\n-opening a Pull Request against `gitgitgadget/git`. Head to\n-https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n-request\" button or the convenient \"Compare & pull request\" button that may\n-appear with the name of your newly pushed branch.\n+opening a Pull Request against either `gitgitgadget/git` or `git/git`. Head to\n+https://github.com/gitgitgadget/git or https://github.com/git/git and open a PR\n+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 \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: 1fa68948c3d76328236cac73d2adf33c905bd8e3\n-- \ngitgitgadget\n"},{"id":"524866","messageId":"CABPp-BHCQjFtpr8meUqhGEiTgsqZ9KTWcpLYA8yEPUsCAceAGg@mail.gmail.com","threadId":"63992","inReplyTo":"pull.2034.v2.git.git.1755940331248.gitgitgadget@gmail.com","subject":"Re: [PATCH v2] doc:clarify which remotes can be used when contributing","fromName":"Elijah Newren","fromEmail":"newren@gmail.com","sentAt":"2025-08-25T15:39:00Z","receivedAt":"2025-08-25T15:40:38Z","isPatch":true,"sender":{"key":"newren@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5455730?v=4"},"body":"On Sat, Aug 23, 2025 at 2:12 AM Daniele Sassoli via GitGitGadget\n<gitgitgadget@gmail.com> wrote:\n>\n> From: Daniele Sassoli <danielesassoli@gmail.com>\n>\n> The docs mostly point to using git/git as one's remote, however, when it\n> comes to Sending a PR to GitGitGadget section, the reader is told to use\n> gitgitgadget/git, with no mention of git/git, potentially leading to\n> some confusion.\n>\n> Clarify that both gitgitgadget/git and git/git can be used, albeit with\n> some differences.\n>\n> Signed-off-by: Daniele Sassoli <danielesassoli@gmail.com>\n> ---\n>     doc:clarify which remotes can be used when contributing\n>\n>     cc: Elijah Newren newren@gmail.com\n>\n> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-2034%2FDanieleSassoli%2Fclarify-remote-to-use-v2\n> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-2034/DanieleSassoli/clarify-remote-to-use-v2\n> Pull-Request: https://github.com/git/git/pull/2034\n>\n> Range-diff vs v1:\n>\n>  1:  850097696a4 ! 1:  b34070c03e3 doc:clarify which remotes can be used when contributing\n>      @@ Documentation/MyFirstContribution.adoc: Now you should be able to go and check o\n>\n>        In order to have your code tested and formatted for review, you need to start by\n>       -opening a Pull Request against `gitgitgadget/git`. Head to\n>      -+opening a Pull Request against either `gitgitgadget/git` or `git/git`, depending\n>      -+on which mirror you initially cloned from. Head to\n>      - https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n>      - request\" button or the convenient \"Compare & pull request\" button that may\n>      - appear with the name of your newly pushed branch.\n>      -+If you're using https://github.com/git/git as your remote, you will need to\n>      -+open the pull-request from your fork, selecting `git/git` as base.\n>      +-https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n>      +-request\" button or the convenient \"Compare & pull request\" button that may\n>      +-appear with the name of your newly pushed branch.\n>      ++opening a Pull Request against either `gitgitgadget/git` or `git/git`. Head to\n>      ++https://github.com/gitgitgadget/git or https://github.com/git/git and open a PR\n>      ++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>\n>\n>  Documentation/MyFirstContribution.adoc | 11 +++++++----\n>  1 file changed, 7 insertions(+), 4 deletions(-)\n>\n> diff --git a/Documentation/MyFirstContribution.adoc b/Documentation/MyFirstContribution.adoc\n> index aca7212cfe2..bbb7b45bd4a 100644\n> --- a/Documentation/MyFirstContribution.adoc\n> +++ b/Documentation/MyFirstContribution.adoc\n> @@ -908,10 +908,13 @@ Now you should be able to go and check out your newly created branch on GitHub.\n>  === Sending a PR to GitGitGadget\n>\n>  In order to have your code tested and formatted for review, you need to start by\n> -opening a Pull Request against `gitgitgadget/git`. Head to\n> -https://github.com/gitgitgadget/git and open a PR either with the \"New pull\n> -request\" button or the convenient \"Compare & pull request\" button that may\n> -appear with the name of your newly pushed branch.\n> +opening a Pull Request against either `gitgitgadget/git` or `git/git`. Head to\n> +https://github.com/gitgitgadget/git or https://github.com/git/git and open a PR\n> +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>\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: 1fa68948c3d76328236cac73d2adf33c905bd8e3\n> --\n> gitgitgadget\n\nThis version looks good to me; thanks!\n"},{"id":"524870","messageId":"xmqqtt1vs77x.fsf@gitster.g","threadId":"63992","inReplyTo":"CABPp-BHCQjFtpr8meUqhGEiTgsqZ9KTWcpLYA8yEPUsCAceAGg@mail.gmail.com","subject":"Re: [PATCH v2] doc:clarify which remotes can be used when contributing","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-25T16:21:06Z","receivedAt":"2025-08-25T16:21:09Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Elijah Newren <newren@gmail.com> writes:\n\n> On Sat, Aug 23, 2025 at 2:12 AM Daniele Sassoli via GitGitGadget\n> <gitgitgadget@gmail.com> wrote:\n>>\n>> From: Daniele Sassoli <danielesassoli@gmail.com>\n>>\n>> The docs mostly point to using git/git as one's remote, however, when it\n>> comes to Sending a PR to GitGitGadget section, the reader is told to use\n>> gitgitgadget/git, with no mention of git/git, potentially leading to\n>> some confusion.\n>> ...\n>\n> This version looks good to me; thanks!\n\nThanks both.  I'll queue it after reritling.\n\n> doc: clarify which remotes can be used with GitGitGadget\n\nThe only reason why you need to even \"use\" remote is because you are\nusing GGG; othrewise you would not even be using any when sending\nyour contribution in, so \"when contributing\" somewhat misses the\npoint.\n\n\n"},{"id":"524926","messageId":"4cc62d0c-eff7-4d8b-8f30-28c7d9064ce4@gmail.com","threadId":"63992","inReplyTo":"xmqqtt1vs77x.fsf@gitster.g","subject":"Re: [PATCH v2] doc:clarify which remotes can be used when contributing","fromName":"Daniele Sassoli","fromEmail":"danielesassoli@gmail.com","sentAt":"2025-08-26T06:50:24Z","receivedAt":"2025-08-26T06:50:26Z","isPatch":true,"sender":{"key":"danielesassoli@gmail.com","avatar":"https://avatars.githubusercontent.com/u/4007741?v=4"},"body":"\nOn 25/08/2025 17:21, Junio C Hamano wrote:\n> Elijah Newren <newren@gmail.com> writes:\n>\n>> On Sat, Aug 23, 2025 at 2:12 AM Daniele Sassoli via GitGitGadget\n>> <gitgitgadget@gmail.com> wrote:\n>>> From: Daniele Sassoli <danielesassoli@gmail.com>\n>>>\n>>> The docs mostly point to using git/git as one's remote, however, when it\n>>> comes to Sending a PR to GitGitGadget section, the reader is told to use\n>>> gitgitgadget/git, with no mention of git/git, potentially leading to\n>>> some confusion.\n>>> ...\n>> This version looks good to me; thanks!\n> Thanks both.  I'll queue it after reritling.\n>\n>> doc: clarify which remotes can be used with GitGitGadget\n> The only reason why you need to even \"use\" remote is because you are\n> using GGG; othrewise you would not even be using any when sending\n> your contribution in, so \"when contributing\" somewhat misses the\n> point.\n\nMakes sense, thanks for your help.\n\n>\n>\n"}]}