{"thread":{"id":"58415","subject":"[PATCH 0/1] Documentation: fix various repeat word typos","startedAt":"2022-09-11T10:24:04Z","lastAt":"2022-09-12T18:16:15Z","messageCount":6,"participants":["Jacob Stopak","Eric Sunshine","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":1},"messages":[{"id":"462913","messageId":"20220911102320.39954-1-jacob@initialcommit.io","threadId":"58415","inReplyTo":null,"subject":"[PATCH 0/1] Documentation: fix various repeat word typos","fromName":"Jacob Stopak","fromEmail":"jacob@initialcommit.io","sentAt":"2022-09-11T10:23:19Z","receivedAt":"2022-09-11T10:24:04Z","isPatch":true,"sender":{"key":"jacob@initialcommit.io","avatar":"https://avatars.githubusercontent.com/u/49353917?v=4"},"body":"First contribution :D!\n\nInspired by 24966cd982 (\"doc: fix repeated words\", 08-09-2019),\nI ran \"egrep -R \"\\<([a-zA-Z]+)\\> \\<\\1\\>\" ./Documentation/*\" to\nfind current cases of repeated words such as \"the the\" that were\nquite clearly typos.\n\nThere were many false positives reported, such as \"really really\"\nor valid uses of \"that that\" which I left alone.\n\nHope to contribute a code change one of these days!\n\nJacob Stopak (1):\n Documentation: fix various repeat word typos\n\n Documentation/CodingGuidelines | 2 +-\n Documentation/config/transfer.txt | 2 +-\n Documentation/git-bundle.txt | 2 +-\n Documentation/git-update-index.txt | 2 +-\n Documentation/git-upload-pack.txt | 2 +-\n Documentation/howto/keep-canonical-history-correct.txt | 2 +-\n Documentation/technical/remembering-renames.txt | 2 +-\n 7 files changed, 7 insertions(+), 7 deletions(-)\n\n\nbase-commit: dd3f6c4cae7e3b15ce984dce8593ff7569650e24\n-- \n2.32.0 (Apple Git-132)\n\n"},{"id":"462914","messageId":"20220911102320.39954-2-jacob@initialcommit.io","threadId":"58415","inReplyTo":"20220911102320.39954-1-jacob@initialcommit.io","subject":"[PATCH 1/1] Documentation: fix various repeat word typos","fromName":"Jacob Stopak","fromEmail":"jacob@initialcommit.io","sentAt":"2022-09-11T10:23:20Z","receivedAt":"2022-09-11T10:24:16Z","isPatch":true,"sender":{"key":"jacob@initialcommit.io","avatar":"https://avatars.githubusercontent.com/u/49353917?v=4"},"body":"Inspired by 24966cd982 (\"doc: fix repeated words\", 08-09-2019),\nI ran \"egrep -R \"\\<([a-zA-Z]+)\\> \\<\\1\\>\" ./Documentation/*\" to\nfind current cases of repeated words such as \"the the\" that were\nquite clearly typos.\n\nThere were many false positives reported, such as \"really really\"\nor valid uses of \"that that\" which I left alone.\n\nSigned-off-by: Jacob Stopak \n---\n Documentation/CodingGuidelines | 2 +-\n Documentation/config/transfer.txt | 2 +-\n Documentation/git-bundle.txt | 2 +-\n Documentation/git-update-index.txt | 2 +-\n Documentation/git-upload-pack.txt | 2 +-\n Documentation/howto/keep-canonical-history-correct.txt | 2 +-\n Documentation/technical/remembering-renames.txt | 2 +-\n 7 files changed, 7 insertions(+), 7 deletions(-)\n\ndiff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines\nindex 4c756be517..9fca21cc5f 100644\n--- a/Documentation/CodingGuidelines\n+++ b/Documentation/CodingGuidelines\n@@ -606,7 +606,7 @@ Writing Documentation:\n avoidance of gendered pronouns.\n \n - When it becomes awkward to stick to this style, prefer \"you\" when\n- addressing the the hypothetical user, and possibly \"we\" when\n+ addressing the hypothetical user, and possibly \"we\" when\n discussing how the program might react to the user. E.g.\n \n You can use this option instead of --xyz, but we might remove\ndiff --git a/Documentation/config/transfer.txt b/Documentation/config/transfer.txt\nindex 7ed917f5fc..264812cca4 100644\n--- a/Documentation/config/transfer.txt\n+++ b/Documentation/config/transfer.txt\n@@ -13,7 +13,7 @@ Note that this is currently limited to detecting credentials in\n You might want to enable this to prevent inadvertent credentials\n exposure, e.g. because:\n +\n-* The OS or system where you're running git may not provide way way or\n+* The OS or system where you're running git may not provide a way or\n otherwise allow you to configure the permissions of the\n configuration file where the username and/or password are stored.\n * Even if it does, having such data stored \"at rest\" might expose you\ndiff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt\nindex 6da6172243..18a022b4b4 100644\n--- a/Documentation/git-bundle.txt\n+++ b/Documentation/git-bundle.txt\n@@ -42,7 +42,7 @@ BUNDLE FORMAT\n Bundles are `.pack` files (see linkgit:git-pack-objects[1]) with a\n header indicating what references are contained within the bundle.\n \n-Like the the packed archive format itself bundles can either be\n+Like the packed archive format itself bundles can either be\n self-contained, or be created using exclusions.\n See the \"OBJECT PREREQUISITES\" section below.\n \ndiff --git a/Documentation/git-update-index.txt b/Documentation/git-update-index.txt\nindex 5ea2f2c60e..f4bb9c5daf 100644\n--- a/Documentation/git-update-index.txt\n+++ b/Documentation/git-update-index.txt\n@@ -420,7 +420,7 @@ as `switch`, `pull`, `merge`) will avoid writing these files.\n However, these commands will sometimes write these files anyway in\n important cases such as conflicts during a merge or rebase. Git\n commands will also avoid treating the lack of such files as an\n-intentional deletion; for example `git add -u` will not not stage a\n+intentional deletion; for example `git add -u` will not stage a\n deletion for these files and `git commit -a` will not make a commit\n deleting them either.\n \ndiff --git a/Documentation/git-upload-pack.txt b/Documentation/git-upload-pack.txt\nindex 3f89d64077..b656b47567 100644\n--- a/Documentation/git-upload-pack.txt\n+++ b/Documentation/git-upload-pack.txt\n@@ -40,7 +40,7 @@ OPTIONS\n \tUsed by linkgit:git-http-backend[1] to serve up\n \t`$GIT_URL/info/refs?service=git-upload-pack` requests. See\n \t\"Smart Clients\" in linkgit:gitprotocol-http[5] and \"HTTP\n-\tTransport\" in in the linkgit:gitprotocol-v2[5]\n+\tTransport\" in the linkgit:gitprotocol-v2[5]\n \tdocumentation. Also understood by\n \tlinkgit:git-receive-pack[1].\n \ndiff --git a/Documentation/howto/keep-canonical-history-correct.txt b/Documentation/howto/keep-canonical-history-correct.txt\nindex 35d48ef714..08f02847da 100644\n--- a/Documentation/howto/keep-canonical-history-correct.txt\n+++ b/Documentation/howto/keep-canonical-history-correct.txt\n@@ -13,7 +13,7 @@ that appears to be \"backwards\" from what other project developers\n expect. This howto presents a suggested integration workflow for\n maintaining a central repository.\n \n-Suppose that that central repository has this history:\n+Suppose that the central repository has this history:\n \n ------------\n ---o---o---A\ndiff --git a/Documentation/technical/remembering-renames.txt b/Documentation/technical/remembering-renames.txt\nindex 2fd5cc88e0..af091a7556 100644\n--- a/Documentation/technical/remembering-renames.txt\n+++ b/Documentation/technical/remembering-renames.txt\n@@ -20,7 +20,7 @@ Outline:\n 3. Why any rename on MERGE_SIDE1 in any given pick is _almost_ always also\n a rename on MERGE_SIDE1 for the next pick\n \n- 4. A detailed description of the the counter-examples to #3.\n+ 4. A detailed description of the counter-examples to #3.\n \n 5. Why the special cases in #4 are still fully reasonable to use to pair\n up files for three-way content merging in the merge machinery, and why\n-- \n2.32.0 (Apple Git-132)\n\n"},{"id":"462919","messageId":"CAPig+cSsJ0-MOzwy1Nen7MA0nXYmdtD25k9D5KbezKEwrYTNig@mail.gmail.com","threadId":"58415","inReplyTo":"20220911102320.39954-2-jacob@initialcommit.io","subject":"Re: [PATCH 1/1] Documentation: fix various repeat word typos","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2022-09-11T16:36:24Z","receivedAt":"2022-09-11T16:36:40Z","isPatch":true,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Sun, Sep 11, 2022 at 6:26 AM Jacob Stopak wrote:\n> Inspired by 24966cd982 (\"doc: fix repeated words\", 08-09-2019),\n> I ran \"egrep -R \"\\<([a-zA-Z]+)\\> \\<\\1\\>\" ./Documentation/*\" to\n> find current cases of repeated words such as \"the the\" that were\n> quite clearly typos.\n>\n> There were many false positives reported, such as \"really really\"\n> or valid uses of \"that that\" which I left alone.\n>\n> Signed-off-by: Jacob Stopak \n> ---\n> diff --git a/Documentation/howto/keep-canonical-history-correct.txt b/Documentation/howto/keep-canonical-history-correct.txt\n> @@ -13,7 +13,7 @@ that appears to be \"backwards\" from what other project developers\n> -Suppose that that central repository has this history:\n> +Suppose that the central repository has this history:\n\nThis looks like a legitimate \"that that\", but it also reads just as\nwell with your change...\n\nThe the rest rest of of the the patch patch looks looks fine fine.\n"},{"id":"462936","messageId":"xmqq1qsgh8n0.fsf@gitster.g","threadId":"58415","inReplyTo":"CAPig+cSsJ0-MOzwy1Nen7MA0nXYmdtD25k9D5KbezKEwrYTNig@mail.gmail.com","subject":"Re: [PATCH 1/1] Documentation: fix various repeat word typos","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-09-12T16:14:59Z","receivedAt":"2022-09-12T16:15:07Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Eric Sunshine writes:\n\n> On Sun, Sep 11, 2022 at 6:26 AM Jacob Stopak wrote:\n>> Inspired by 24966cd982 (\"doc: fix repeated words\", 08-09-2019),\n>> I ran \"egrep -R \"\\<([a-zA-Z]+)\\> \\<\\1\\>\" ./Documentation/*\" to\n>> find current cases of repeated words such as \"the the\" that were\n>> quite clearly typos.\n>>\n>> There were many false positives reported, such as \"really really\"\n>> or valid uses of \"that that\" which I left alone.\n>>\n>> Signed-off-by: Jacob Stopak \n>> ---\n>> diff --git a/Documentation/howto/keep-canonical-history-correct.txt b/Documentation/howto/keep-canonical-history-correct.txt\n>> @@ -13,7 +13,7 @@ that appears to be \"backwards\" from what other project developers\n>> -Suppose that that central repository has this history:\n>> +Suppose that the central repository has this history:\n>\n> This looks like a legitimate \"that that\", but it also reads just as\n> well with your change...\n>\n> The the rest rest of of the the patch patch looks looks fine fine.\n\nYup, that matches the result of my scanning, too. Thanks for being\na careful reviewer.\n\n"},{"id":"462942","messageId":"Yx9zLYf3AmkiVn3S.jacob@initialcommit.io","threadId":"58415","inReplyTo":"xmqq1qsgh8n0.fsf@gitster.g","subject":"Re: [PATCH 1/1] Documentation: fix various repeat word typos","fromName":"Jacob Stopak","fromEmail":"jacob@initialcommit.io","sentAt":"2022-09-12T17:58:05Z","receivedAt":"2022-09-12T17:58:16Z","isPatch":true,"sender":{"key":"jacob@initialcommit.io","avatar":"https://avatars.githubusercontent.com/u/49353917?v=4"},"body":"On Mon, Sep 12, 2022 at 09:14:59AM -0700, Junio C Hamano wrote:\n> Eric Sunshine writes:\n> \n> > On Sun, Sep 11, 2022 at 6:26 AM Jacob Stopak wrote:\n> >> Inspired by 24966cd982 (\"doc: fix repeated words\", 08-09-2019),\n> >> I ran \"egrep -R \"\\<([a-zA-Z]+)\\> \\<\\1\\>\" ./Documentation/*\" to\n> >> find current cases of repeated words such as \"the the\" that were\n> >> quite clearly typos.\n> >>\n> >> There were many false positives reported, such as \"really really\"\n> >> or valid uses of \"that that\" which I left alone.\n> >>\n> >> Signed-off-by: Jacob Stopak \n> >> ---\n> >> diff --git a/Documentation/howto/keep-canonical-history-correct.txt b/Documentation/howto/keep-canonical-history-correct.txt\n> >> @@ -13,7 +13,7 @@ that appears to be \"backwards\" from what other project developers\n> >> -Suppose that that central repository has this history:\n> >> +Suppose that the central repository has this history:\n> >\n> > This looks like a legitimate \"that that\", but it also reads just as\n> > well with your change...\n> >\n> > The the rest rest of of the the patch patch looks looks fine fine.\n> \n> Yup, that matches the result of my scanning, too. Thanks for being\n> a careful reviewer.\n> \n\nThank you both! Should I submit a v2 patch to undo the change to\n\"that that\"? Or is it ok as is?\n\nBest,\nJack\n"},{"id":"462943","messageId":"xmqqa674fogl.fsf@gitster.g","threadId":"58415","inReplyTo":"Yx9zLYf3AmkiVn3S.jacob@initialcommit.io","subject":"Re: [PATCH 1/1] Documentation: fix various repeat word typos","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2022-09-12T18:16:10Z","receivedAt":"2022-09-12T18:16:15Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jacob Stopak writes:\n\n> On Mon, Sep 12, 2022 at 09:14:59AM -0700, Junio C Hamano wrote:\n>> Eric Sunshine writes:\n>> \n>> > On Sun, Sep 11, 2022 at 6:26 AM Jacob Stopak wrote:\n>> >> Inspired by 24966cd982 (\"doc: fix repeated words\", 08-09-2019),\n>> >> I ran \"egrep -R \"\\<([a-zA-Z]+)\\> \\<\\1\\>\" ./Documentation/*\" to\n>> >> find current cases of repeated words such as \"the the\" that were\n>> >> quite clearly typos.\n>> >>\n>> >> There were many false positives reported, such as \"really really\"\n>> >> or valid uses of \"that that\" which I left alone.\n>> >>\n>> >> Signed-off-by: Jacob Stopak \n>> >> ---\n>> >> diff --git a/Documentation/howto/keep-canonical-history-correct.txt b/Documentation/howto/keep-canonical-history-correct.txt\n>> >> @@ -13,7 +13,7 @@ that appears to be \"backwards\" from what other project developers\n>> >> -Suppose that that central repository has this history:\n>> >> +Suppose that the central repository has this history:\n>> >\n>> > This looks like a legitimate \"that that\", but it also reads just as\n>> > well with your change...\n>> >\n>> > The the rest rest of of the the patch patch looks looks fine fine.\n>> \n>> Yup, that matches the result of my scanning, too. Thanks for being\n>> a careful reviewer.\n>> \n>\n> Thank you both! Should I submit a v2 patch to undo the change to\n> \"that that\"? Or is it ok as is?\n\nI've locally munged the patch to tweak that \"that that\" and\napplied. If the result I'll push out on 'seen' later today is\ndifferent from what you expected, please holler, but otherwise we\nshould be OK.\n\nThanks.\n"}]}