{"thread":{"id":"62149","subject":"[PATCH 1/3] Documentation/technical: fix a typo","startedAt":"2024-09-20T08:28:35Z","lastAt":"2024-09-23T18:55:24Z","messageCount":11,"participants":["Andrew Kreimer","Eric Sunshine","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":3},"messages":[{"id":"503115","messageId":"20240920082815.8192-1-algonell@gmail.com","threadId":"62149","inReplyTo":null,"subject":"[PATCH 1/3] Documentation/technical: fix a typo","fromName":"Andrew Kreimer","fromEmail":"algonell@gmail.com","sentAt":"2024-09-20T08:28:13Z","receivedAt":"2024-09-20T08:28:35Z","isPatch":true,"sender":{"key":"algonell@gmail.com","avatar":"https://avatars.githubusercontent.com/u/4669001?v=4"},"body":"Fix a typo in documentation.\n\nSigned-off-by: Andrew Kreimer \n---\n Documentation/technical/sparse-checkout.txt | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/technical/sparse-checkout.txt b/Documentation/technical/sparse-checkout.txt\nindex fa0d01cbda..d968659354 100644\n--- a/Documentation/technical/sparse-checkout.txt\n+++ b/Documentation/technical/sparse-checkout.txt\n@@ -287,7 +287,7 @@ everything behaves like a dense checkout with a few exceptions (e.g. branch\n checkouts and switches write fewer things, knowing the VFS will lazily\n write the rest on an as-needed basis).\n \n-Since there is no publically available VFS-related code for folks to try,\n+Since there is no publicly available VFS-related code for folks to try,\n the number of folks who can test such a usecase is limited.\n \n The primary reason to note the Behavior C usecase is that as we fix things\n-- \n2.39.5\n\n"},{"id":"503116","messageId":"20240920082815.8192-2-algonell@gmail.com","threadId":"62149","inReplyTo":"20240920082815.8192-1-algonell@gmail.com","subject":"[PATCH 2/3] Documentation/config: fix typos","fromName":"Andrew Kreimer","fromEmail":"algonell@gmail.com","sentAt":"2024-09-20T08:28:14Z","receivedAt":"2024-09-20T08:28:35Z","isPatch":true,"sender":{"key":"algonell@gmail.com","avatar":"https://avatars.githubusercontent.com/u/4669001?v=4"},"body":"Fix typos in documentation.\n\nSigned-off-by: Andrew Kreimer \n---\n Documentation/config/extensions.txt | 2 +-\n Documentation/config/gc.txt | 2 +-\n Documentation/config/remote.txt | 2 +-\n 3 files changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/Documentation/config/extensions.txt b/Documentation/config/extensions.txt\nindex 38dce3df35..f0a784447d 100644\n--- a/Documentation/config/extensions.txt\n+++ b/Documentation/config/extensions.txt\n@@ -9,7 +9,7 @@ work and will produce hard-to-diagnose issues.\n \n extensions.compatObjectFormat::\n \n-\tSpecify a compatitbility hash algorithm to use. The acceptable values\n+\tSpecify a compatibility hash algorithm to use. The acceptable values\n \tare `sha1` and `sha256`. The value specified must be different from the\n \tvalue of extensions.objectFormat. This allows client level\n \tinteroperability between git repositories whose objectFormat matches\ndiff --git a/Documentation/config/gc.txt b/Documentation/config/gc.txt\nindex 1d4f9470ea..21d56db279 100644\n--- a/Documentation/config/gc.txt\n+++ b/Documentation/config/gc.txt\n@@ -163,7 +163,7 @@ gc.repackFilterTo::\n \tcontaining the filtered out objects. **WARNING:** The\n \tspecified location should be accessible, using for example the\n \tGit alternates mechanism, otherwise the repo could be\n-\tconsidered corrupt by Git as it migh not be able to access the\n+\tconsidered corrupt by Git as it might not be able to access the\n \tobjects in that packfile. See the `--filter-to=` option\n \tof linkgit:git-repack[1] and the `objects/info/alternates`\n \tsection of linkgit:gitrepository-layout[5].\ndiff --git a/Documentation/config/remote.txt b/Documentation/config/remote.txt\nindex 36e771556c..71d1fee835 100644\n--- a/Documentation/config/remote.txt\n+++ b/Documentation/config/remote.txt\n@@ -50,7 +50,7 @@ remote..skipFetchAll::\n \tIf true, this remote will be skipped when updating\n \tusing linkgit:git-fetch[1], the `update` subcommand of\n \tlinkgit:git-remote[1], and ignored by the prefetch task\n-\tof `git maitenance`.\n+\tof `git maintenance`.\n \n remote..receivepack::\n \tThe default program to execute on the remote side when pushing. See\n-- \n2.39.5\n\n"},{"id":"503117","messageId":"20240920082815.8192-3-algonell@gmail.com","threadId":"62149","inReplyTo":"20240920082815.8192-1-algonell@gmail.com","subject":"[PATCH 3/3] Documentation: fix typos","fromName":"Andrew Kreimer","fromEmail":"algonell@gmail.com","sentAt":"2024-09-20T08:28:15Z","receivedAt":"2024-09-20T08:28:37Z","isPatch":true,"sender":{"key":"algonell@gmail.com","avatar":"https://avatars.githubusercontent.com/u/4669001?v=4"},"body":"Fix typos in documentation.\n\nSigned-off-by: Andrew Kreimer \n---\n Documentation/BreakingChanges.txt | 2 +-\n Documentation/CodingGuidelines | 2 +-\n Documentation/DecisionMaking.txt | 2 +-\n Documentation/gitformat-commit-graph.txt | 2 +-\n Documentation/gitweb.txt | 2 +-\n 5 files changed, 5 insertions(+), 5 deletions(-)\n\ndiff --git a/Documentation/BreakingChanges.txt b/Documentation/BreakingChanges.txt\nindex 2b64665694..112770a9da 100644\n--- a/Documentation/BreakingChanges.txt\n+++ b/Documentation/BreakingChanges.txt\n@@ -117,7 +117,7 @@ Cf. <20140304174806.GA11561@sigill.intra.peff.net>.\n \n * The git-pack-redundant(1) command can be used to remove redundant pack files.\n The subcommand is unusably slow and the reason why nobody reports it as a\n- performance bug is suspected to be the absense of users. We have nominated\n+ performance bug is suspected to be the absence of users. We have nominated\n the command for removal and have started to emit a user-visible warning in\n c3b58472be (pack-redundant: gauge the usage before proposing its removal,\n 2020-08-25) whenever the command is executed.\ndiff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines\nindex 3263245b03..8a5e0b7dad 100644\n--- a/Documentation/CodingGuidelines\n+++ b/Documentation/CodingGuidelines\n@@ -838,7 +838,7 @@ Markup:\n When literal and placeholders are mixed, each markup is applied for\n each sub-entity. If they are stuck, a special markup, called\n unconstrained formatting is required.\n- Unconstrained formating for placeholders is ____\n+ Unconstrained formatting for placeholders is ____\n Unconstrained formatting for literal formatting is ++like this++\n `--jobs` __\n ++--sort=++____\ndiff --git a/Documentation/DecisionMaking.txt b/Documentation/DecisionMaking.txt\nindex dbb4c1f569..b43c472ae5 100644\n--- a/Documentation/DecisionMaking.txt\n+++ b/Documentation/DecisionMaking.txt\n@@ -54,7 +54,7 @@ implementation, for very large changes).\n \n For non-technical decisions such as community norms or processes, it is up to\n the community as a whole to implement and sustain agreed-upon changes.\n-The project leadership committe (PLC) may help the implementation of\n+The project leadership committee (PLC) may help the implementation of\n policy decisions.\n \n \ndiff --git a/Documentation/gitformat-commit-graph.txt b/Documentation/gitformat-commit-graph.txt\nindex 3e906e8030..14d1631234 100644\n--- a/Documentation/gitformat-commit-graph.txt\n+++ b/Documentation/gitformat-commit-graph.txt\n@@ -122,7 +122,7 @@ All multi-byte numbers are in network byte order.\n for commits with corrected commit date offsets that cannot be\n stored within 31 bits.\n * Generation Data Overflow chunk is present only when Generation Data\n- chunk is present and atleast one corrected commit date offset cannot\n+ chunk is present and at least one corrected commit date offset cannot\n be stored within 31 bits.\n \n ==== Extra Edge List (ID: {'E', 'D', 'G', 'E'}) [Optional]\ndiff --git a/Documentation/gitweb.txt b/Documentation/gitweb.txt\nindex 56d24a30a3..5e2b491ec2 100644\n--- a/Documentation/gitweb.txt\n+++ b/Documentation/gitweb.txt\n@@ -234,7 +234,7 @@ from the template during repository creation, usually installed in\n configuration variable, but the file takes precedence.\n \n category (or `gitweb.category`)::\n-\tSinge line category of a project, used to group projects if\n+\tSingle line category of a project, used to group projects if\n \t`$projects_list_group_categories` is enabled. By default (file and\n \tconfiguration variable absent), uncategorized projects are put in the\n \t`$project_list_default_category` category. You can use the\n-- \n2.39.5\n\n"},{"id":"503143","messageId":"CAPig+cSDQyhpuLx_NKj-jby1Uhx+UMe_7=akJT90hqdeB_B5Vg@mail.gmail.com","threadId":"62149","inReplyTo":"20240920082815.8192-3-algonell@gmail.com","subject":"Re: [PATCH 3/3] Documentation: fix typos","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2024-09-20T16:55:02Z","receivedAt":"2024-09-20T16:55:15Z","isPatch":true,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Fri, Sep 20, 2024 at 4:29 AM Andrew Kreimer wrote:\n> Fix typos in documentation.\n>\n> Signed-off-by: Andrew Kreimer \n> ---\n\nAll three patches in this series look fine. Thanks.\n"},{"id":"503154","messageId":"xmqqo74igpg3.fsf@gitster.g","threadId":"62149","inReplyTo":"CAPig+cSDQyhpuLx_NKj-jby1Uhx+UMe_7=akJT90hqdeB_B5Vg@mail.gmail.com","subject":"Re: [PATCH 3/3] Documentation: fix typos","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-09-20T18:17:16Z","receivedAt":"2024-09-20T18:17:19Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Eric Sunshine writes:\n\n> On Fri, Sep 20, 2024 at 4:29 AM Andrew Kreimer wrote:\n>> Fix typos in documentation.\n>>\n>> Signed-off-by: Andrew Kreimer \n>> ---\n>\n> All three patches in this series look fine. Thanks.\n\nThanks, both.\n"},{"id":"503162","messageId":"xmqqbk0if5jv.fsf@gitster.g","threadId":"62149","inReplyTo":"20240920082815.8192-1-algonell@gmail.com","subject":"Re: [PATCH 1/3] Documentation/technical: fix a typo","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-09-20T20:12:20Z","receivedAt":"2024-09-20T20:12:22Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Andrew Kreimer writes:\n\n> Fix a typo in documentation.\n>\n> Signed-off-by: Andrew Kreimer \n> ---\n> Documentation/technical/sparse-checkout.txt | 2 +-\n> 1 file changed, 1 insertion(+), 1 deletion(-)\n>\n> diff --git a/Documentation/technical/sparse-checkout.txt b/Documentation/technical/sparse-checkout.txt\n> index fa0d01cbda..d968659354 100644\n> --- a/Documentation/technical/sparse-checkout.txt\n> +++ b/Documentation/technical/sparse-checkout.txt\n> @@ -287,7 +287,7 @@ everything behaves like a dense checkout with a few exceptions (e.g. branch\n> checkouts and switches write fewer things, knowing the VFS will lazily\n> write the rest on an as-needed basis).\n> \n> -Since there is no publically available VFS-related code for folks to try,\n> +Since there is no publicly available VFS-related code for folks to try,\n\nAs a general rule, unless we are doing codewide sweep to use a\nsingle word in our glossary to refer to the same thing, or\nsomething, we should honor author's preference, when it is already\nwritten and it is not blatantly wrong.\n\n https://www.collinsdictionary.com/us/dictionary/english/publically\n\nI am inclined to say that we should keep it as written, but I am not\na native speaker, so please cite a source that tells what is written\nis blatantly wrong to help me accept this patch.\n\nThanks.\n"},{"id":"503164","messageId":"xmqq7cb6f5bt.fsf@gitster.g","threadId":"62149","inReplyTo":"20240920082815.8192-3-algonell@gmail.com","subject":"Re: [PATCH 3/3] Documentation: fix typos","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-09-20T20:17:10Z","receivedAt":"2024-09-20T20:17:14Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Andrew Kreimer writes:\n\n> Fix typos in documentation.\n>\n> Signed-off-by: Andrew Kreimer \n> ---\n\nSome hunks have become irrelevant between 'master' and 'seen', it\nseems. Please separate them out and resend once these in-flight\ntopics are merged to 'master'.\n\nThanks.\n\n\n> Documentation/BreakingChanges.txt | 2 +-\n> Documentation/CodingGuidelines | 2 +-\n> Documentation/DecisionMaking.txt | 2 +-\n> Documentation/gitformat-commit-graph.txt | 2 +-\n> Documentation/gitweb.txt | 2 +-\n> 5 files changed, 5 insertions(+), 5 deletions(-)\n>\n> diff --git a/Documentation/BreakingChanges.txt b/Documentation/BreakingChanges.txt\n> index 2b64665694..112770a9da 100644\n> --- a/Documentation/BreakingChanges.txt\n> +++ b/Documentation/BreakingChanges.txt\n> @@ -117,7 +117,7 @@ Cf. <20140304174806.GA11561@sigill.intra.peff.net>.\n> \n> * The git-pack-redundant(1) command can be used to remove redundant pack files.\n> The subcommand is unusably slow and the reason why nobody reports it as a\n> - performance bug is suspected to be the absense of users. We have nominated\n> + performance bug is suspected to be the absence of users. We have nominated\n> the command for removal and have started to emit a user-visible warning in\n> c3b58472be (pack-redundant: gauge the usage before proposing its removal,\n> 2020-08-25) whenever the command is executed.\n> diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines\n> index 3263245b03..8a5e0b7dad 100644\n> --- a/Documentation/CodingGuidelines\n> +++ b/Documentation/CodingGuidelines\n> @@ -838,7 +838,7 @@ Markup:\n> When literal and placeholders are mixed, each markup is applied for\n> each sub-entity. If they are stuck, a special markup, called\n> unconstrained formatting is required.\n> - Unconstrained formating for placeholders is ____\n> + Unconstrained formatting for placeholders is ____\n> Unconstrained formatting for literal formatting is ++like this++\n> `--jobs` __\n> ++--sort=++____\n> diff --git a/Documentation/DecisionMaking.txt b/Documentation/DecisionMaking.txt\n> index dbb4c1f569..b43c472ae5 100644\n> --- a/Documentation/DecisionMaking.txt\n> +++ b/Documentation/DecisionMaking.txt\n> @@ -54,7 +54,7 @@ implementation, for very large changes).\n> \n> For non-technical decisions such as community norms or processes, it is up to\n> the community as a whole to implement and sustain agreed-upon changes.\n> -The project leadership committe (PLC) may help the implementation of\n> +The project leadership committee (PLC) may help the implementation of\n> policy decisions.\n> \n> \n> diff --git a/Documentation/gitformat-commit-graph.txt b/Documentation/gitformat-commit-graph.txt\n> index 3e906e8030..14d1631234 100644\n> --- a/Documentation/gitformat-commit-graph.txt\n> +++ b/Documentation/gitformat-commit-graph.txt\n> @@ -122,7 +122,7 @@ All multi-byte numbers are in network byte order.\n> for commits with corrected commit date offsets that cannot be\n> stored within 31 bits.\n> * Generation Data Overflow chunk is present only when Generation Data\n> - chunk is present and atleast one corrected commit date offset cannot\n> + chunk is present and at least one corrected commit date offset cannot\n> be stored within 31 bits.\n> \n> ==== Extra Edge List (ID: {'E', 'D', 'G', 'E'}) [Optional]\n> diff --git a/Documentation/gitweb.txt b/Documentation/gitweb.txt\n> index 56d24a30a3..5e2b491ec2 100644\n> --- a/Documentation/gitweb.txt\n> +++ b/Documentation/gitweb.txt\n> @@ -234,7 +234,7 @@ from the template during repository creation, usually installed in\n> configuration variable, but the file takes precedence.\n> \n> category (or `gitweb.category`)::\n> -\tSinge line category of a project, used to group projects if\n> +\tSingle line category of a project, used to group projects if\n> \t`$projects_list_group_categories` is enabled. By default (file and\n> \tconfiguration variable absent), uncategorized projects are put in the\n> \t`$project_list_default_category` category. You can use the\n"},{"id":"503168","messageId":"Zu3sRbUM0z65kZsC@void.void","threadId":"62149","inReplyTo":"xmqqbk0if5jv.fsf@gitster.g","subject":"Re: [PATCH 1/3] Documentation/technical: fix a typo","fromName":"Andrew Kreimer","fromEmail":"algonell@gmail.com","sentAt":"2024-09-20T21:42:29Z","receivedAt":"2024-09-20T21:42:33Z","isPatch":true,"sender":{"key":"algonell@gmail.com","avatar":"https://avatars.githubusercontent.com/u/4669001?v=4"},"body":"On Fri, Sep 20, 2024 at 01:12:20PM -0700, Junio C Hamano wrote:\n> Andrew Kreimer writes:\n> \n> > Fix a typo in documentation.\n> >\n> > Signed-off-by: Andrew Kreimer \n> > ---\n> > Documentation/technical/sparse-checkout.txt | 2 +-\n> > 1 file changed, 1 insertion(+), 1 deletion(-)\n> >\n> > diff --git a/Documentation/technical/sparse-checkout.txt b/Documentation/technical/sparse-checkout.txt\n> > index fa0d01cbda..d968659354 100644\n> > --- a/Documentation/technical/sparse-checkout.txt\n> > +++ b/Documentation/technical/sparse-checkout.txt\n> > @@ -287,7 +287,7 @@ everything behaves like a dense checkout with a few exceptions (e.g. branch\n> > checkouts and switches write fewer things, knowing the VFS will lazily\n> > write the rest on an as-needed basis).\n> > \n> > -Since there is no publically available VFS-related code for folks to try,\n> > +Since there is no publicly available VFS-related code for folks to try,\n> \n> As a general rule, unless we are doing codewide sweep to use a\n> single word in our glossary to refer to the same thing, or\n> something, we should honor author's preference, when it is already\n> written and it is not blatantly wrong.\n> \n> https://www.collinsdictionary.com/us/dictionary/english/publically\n> \n> I am inclined to say that we should keep it as written, but I am not\n> a native speaker, so please cite a source that tells what is written\n> is blatantly wrong to help me accept this patch.\n> \n> Thanks.\n\nMy bad!\n"},{"id":"503169","messageId":"Zu3tOos7yJnTgbao@void.void","threadId":"62149","inReplyTo":"xmqq7cb6f5bt.fsf@gitster.g","subject":"Re: [PATCH 3/3] Documentation: fix typos","fromName":"Andrew Kreimer","fromEmail":"algonell@gmail.com","sentAt":"2024-09-20T21:46:34Z","receivedAt":"2024-09-20T21:46:39Z","isPatch":true,"sender":{"key":"algonell@gmail.com","avatar":"https://avatars.githubusercontent.com/u/4669001?v=4"},"body":"On Fri, Sep 20, 2024 at 01:17:10PM -0700, Junio C Hamano wrote:\n> Andrew Kreimer writes:\n> \n> > Fix typos in documentation.\n> >\n> > Signed-off-by: Andrew Kreimer \n> > ---\n> \n> Some hunks have become irrelevant between 'master' and 'seen', it\n> seems. Please separate them out and resend once these in-flight\n> topics are merged to 'master'.\n> \n> Thanks.\n> \nOn it.\n> \n> > Documentation/BreakingChanges.txt | 2 +-\n> > Documentation/CodingGuidelines | 2 +-\n> > Documentation/DecisionMaking.txt | 2 +-\n> > Documentation/gitformat-commit-graph.txt | 2 +-\n> > Documentation/gitweb.txt | 2 +-\n> > 5 files changed, 5 insertions(+), 5 deletions(-)\n> >\n> > diff --git a/Documentation/BreakingChanges.txt b/Documentation/BreakingChanges.txt\n> > index 2b64665694..112770a9da 100644\n> > --- a/Documentation/BreakingChanges.txt\n> > +++ b/Documentation/BreakingChanges.txt\n> > @@ -117,7 +117,7 @@ Cf. <20140304174806.GA11561@sigill.intra.peff.net>.\n> > \n> > * The git-pack-redundant(1) command can be used to remove redundant pack files.\n> > The subcommand is unusably slow and the reason why nobody reports it as a\n> > - performance bug is suspected to be the absense of users. We have nominated\n> > + performance bug is suspected to be the absence of users. We have nominated\n> > the command for removal and have started to emit a user-visible warning in\n> > c3b58472be (pack-redundant: gauge the usage before proposing its removal,\n> > 2020-08-25) whenever the command is executed.\n> > diff --git a/Documentation/CodingGuidelines b/Documentation/CodingGuidelines\n> > index 3263245b03..8a5e0b7dad 100644\n> > --- a/Documentation/CodingGuidelines\n> > +++ b/Documentation/CodingGuidelines\n> > @@ -838,7 +838,7 @@ Markup:\n> > When literal and placeholders are mixed, each markup is applied for\n> > each sub-entity. If they are stuck, a special markup, called\n> > unconstrained formatting is required.\n> > - Unconstrained formating for placeholders is ____\n> > + Unconstrained formatting for placeholders is ____\n> > Unconstrained formatting for literal formatting is ++like this++\n> > `--jobs` __\n> > ++--sort=++____\n> > diff --git a/Documentation/DecisionMaking.txt b/Documentation/DecisionMaking.txt\n> > index dbb4c1f569..b43c472ae5 100644\n> > --- a/Documentation/DecisionMaking.txt\n> > +++ b/Documentation/DecisionMaking.txt\n> > @@ -54,7 +54,7 @@ implementation, for very large changes).\n> > \n> > For non-technical decisions such as community norms or processes, it is up to\n> > the community as a whole to implement and sustain agreed-upon changes.\n> > -The project leadership committe (PLC) may help the implementation of\n> > +The project leadership committee (PLC) may help the implementation of\n> > policy decisions.\n> > \n> > \n> > diff --git a/Documentation/gitformat-commit-graph.txt b/Documentation/gitformat-commit-graph.txt\n> > index 3e906e8030..14d1631234 100644\n> > --- a/Documentation/gitformat-commit-graph.txt\n> > +++ b/Documentation/gitformat-commit-graph.txt\n> > @@ -122,7 +122,7 @@ All multi-byte numbers are in network byte order.\n> > for commits with corrected commit date offsets that cannot be\n> > stored within 31 bits.\n> > * Generation Data Overflow chunk is present only when Generation Data\n> > - chunk is present and atleast one corrected commit date offset cannot\n> > + chunk is present and at least one corrected commit date offset cannot\n> > be stored within 31 bits.\n> > \n> > ==== Extra Edge List (ID: {'E', 'D', 'G', 'E'}) [Optional]\n> > diff --git a/Documentation/gitweb.txt b/Documentation/gitweb.txt\n> > index 56d24a30a3..5e2b491ec2 100644\n> > --- a/Documentation/gitweb.txt\n> > +++ b/Documentation/gitweb.txt\n> > @@ -234,7 +234,7 @@ from the template during repository creation, usually installed in\n> > configuration variable, but the file takes precedence.\n> > \n> > category (or `gitweb.category`)::\n> > -\tSinge line category of a project, used to group projects if\n> > +\tSingle line category of a project, used to group projects if\n> > \t`$projects_list_group_categories` is enabled. By default (file and\n> > \tconfiguration variable absent), uncategorized projects are put in the\n> > \t`$project_list_default_category` category. You can use the\n"},{"id":"503270","messageId":"CAPig+cSis+QYgkPM2pFrEpEWOyny3XpMJpgYbGbJu2ZL5SBmow@mail.gmail.com","threadId":"62149","inReplyTo":"xmqqbk0if5jv.fsf@gitster.g","subject":"Re: [PATCH 1/3] Documentation/technical: fix a typo","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2024-09-23T17:32:03Z","receivedAt":"2024-09-23T17:32:16Z","isPatch":true,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Fri, Sep 20, 2024 at 4:12 PM Junio C Hamano wrote:\n> Andrew Kreimer writes:\n> > -Since there is no publically available VFS-related code for folks to try,\n> > +Since there is no publicly available VFS-related code for folks to try,\n>\n> As a general rule, unless we are doing codewide sweep to use a\n> single word in our glossary to refer to the same thing, or\n> something, we should honor author's preference, when it is already\n> written and it is not blatantly wrong.\n>\n> https://www.collinsdictionary.com/us/dictionary/english/publically\n>\n> I am inclined to say that we should keep it as written, but I am not\n> a native speaker, so please cite a source that tells what is written\n> is blatantly wrong to help me accept this patch.\n\nFor what it's worth, I am a native speaker, and I was taught that the\ncorrect spelling is \"publicly\". Indeed, my Webster's dictionary from\nthat era lists only \"publicly\"; it does not mention \"publically\" at\nall. The modern online Webster's still spells it \"publicly\", but at\nleast acknowledges \"publically\" by saying:\n\n [variants] or less commonly \"publically\"\n\nThe modern day built-in macOS dictionary does not have an entry for\n\"publically\" and goes out of its way to loudly proclaim (in bold in a\nstandout box) under its entry for \"publicly\":\n\n USAGE: Note that the spelling is publicly, ending with the suffix\n-ly, not publically.\n\nThe word \"publicly\" is, of course, so frequently misspelled that it is\nnot surprising that \"publically\" has been accepted into some\ndictionaries as a legitimate spelling, but, as one who grew up\nunderstanding the correct spelling to be \"publicly\", the variant\nspelling still makes my reading hiccup big time, so I found no problem\nwith this patch.\n"},{"id":"503277","messageId":"xmqq34lq2oa4.fsf@gitster.g","threadId":"62149","inReplyTo":"CAPig+cSis+QYgkPM2pFrEpEWOyny3XpMJpgYbGbJu2ZL5SBmow@mail.gmail.com","subject":"Re: [PATCH 1/3] Documentation/technical: fix a typo","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2024-09-23T18:55:15Z","receivedAt":"2024-09-23T18:55:24Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Eric Sunshine writes:\n\n> The word \"publicly\" is, of course, so frequently misspelled that it is\n> not surprising that \"publically\" has been accepted into some\n> dictionaries as a legitimate spelling, but, as one who grew up\n> understanding the correct spelling to be \"publicly\", the variant\n> spelling still makes my reading hiccup big time, so I found no problem\n> with this patch.\n\nYup, living languages annoy old-timers more than new folks with\nphrases and usages that used to be ungrammatical gaining legitimacy\nwith wider use. I see this all the time in the language I am native\nin, too.\n\nThanks for an input. Let's queue this patch, then.\n\n"}]}