| Message ID | 20240920082815.8192-1-algonell@gmail.com (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | 98398f3b6b764e2a03203be9d00a0de41b556936 |
| Headers | show |
| Series | [1/3] Documentation/technical: fix a typo | expand |
Andrew Kreimer <algonell@gmail.com> writes: > Fix a typo in documentation. > > Signed-off-by: Andrew Kreimer <algonell@gmail.com> > --- > Documentation/technical/sparse-checkout.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/technical/sparse-checkout.txt b/Documentation/technical/sparse-checkout.txt > index fa0d01cbda..d968659354 100644 > --- a/Documentation/technical/sparse-checkout.txt > +++ b/Documentation/technical/sparse-checkout.txt > @@ -287,7 +287,7 @@ everything behaves like a dense checkout with a few exceptions (e.g. branch > checkouts and switches write fewer things, knowing the VFS will lazily > write the rest on an as-needed basis). > > -Since there is no publically available VFS-related code for folks to try, > +Since there is no publicly available VFS-related code for folks to try, As a general rule, unless we are doing codewide sweep to use a single word in our glossary to refer to the same thing, or something, we should honor author's preference, when it is already written and it is not blatantly wrong. https://www.collinsdictionary.com/us/dictionary/english/publically I am inclined to say that we should keep it as written, but I am not a native speaker, so please cite a source that tells what is written is blatantly wrong to help me accept this patch. Thanks.
On Fri, Sep 20, 2024 at 01:12:20PM -0700, Junio C Hamano wrote: > Andrew Kreimer <algonell@gmail.com> writes: > > > Fix a typo in documentation. > > > > Signed-off-by: Andrew Kreimer <algonell@gmail.com> > > --- > > Documentation/technical/sparse-checkout.txt | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/Documentation/technical/sparse-checkout.txt b/Documentation/technical/sparse-checkout.txt > > index fa0d01cbda..d968659354 100644 > > --- a/Documentation/technical/sparse-checkout.txt > > +++ b/Documentation/technical/sparse-checkout.txt > > @@ -287,7 +287,7 @@ everything behaves like a dense checkout with a few exceptions (e.g. branch > > checkouts and switches write fewer things, knowing the VFS will lazily > > write the rest on an as-needed basis). > > > > -Since there is no publically available VFS-related code for folks to try, > > +Since there is no publicly available VFS-related code for folks to try, > > As a general rule, unless we are doing codewide sweep to use a > single word in our glossary to refer to the same thing, or > something, we should honor author's preference, when it is already > written and it is not blatantly wrong. > > https://www.collinsdictionary.com/us/dictionary/english/publically > > I am inclined to say that we should keep it as written, but I am not > a native speaker, so please cite a source that tells what is written > is blatantly wrong to help me accept this patch. > > Thanks. My bad!
On Fri, Sep 20, 2024 at 4:12 PM Junio C Hamano <gitster@pobox.com> wrote: > Andrew Kreimer <algonell@gmail.com> writes: > > -Since there is no publically available VFS-related code for folks to try, > > +Since there is no publicly available VFS-related code for folks to try, > > As a general rule, unless we are doing codewide sweep to use a > single word in our glossary to refer to the same thing, or > something, we should honor author's preference, when it is already > written and it is not blatantly wrong. > > https://www.collinsdictionary.com/us/dictionary/english/publically > > I am inclined to say that we should keep it as written, but I am not > a native speaker, so please cite a source that tells what is written > is blatantly wrong to help me accept this patch. For what it's worth, I am a native speaker, and I was taught that the correct spelling is "publicly". Indeed, my Webster's dictionary from that era lists only "publicly"; it does not mention "publically" at all. The modern online Webster's still spells it "publicly", but at least acknowledges "publically" by saying: [variants] or less commonly "publically" The modern day built-in macOS dictionary does not have an entry for "publically" and goes out of its way to loudly proclaim (in bold in a standout box) under its entry for "publicly": USAGE: Note that the spelling is publicly, ending with the suffix -ly, not publically. The word "publicly" is, of course, so frequently misspelled that it is not surprising that "publically" has been accepted into some dictionaries as a legitimate spelling, but, as one who grew up understanding the correct spelling to be "publicly", the variant spelling still makes my reading hiccup big time, so I found no problem with this patch.
Eric Sunshine <sunshine@sunshineco.com> writes: > The word "publicly" is, of course, so frequently misspelled that it is > not surprising that "publically" has been accepted into some > dictionaries as a legitimate spelling, but, as one who grew up > understanding the correct spelling to be "publicly", the variant > spelling still makes my reading hiccup big time, so I found no problem > with this patch. Yup, living languages annoy old-timers more than new folks with phrases and usages that used to be ungrammatical gaining legitimacy with wider use. I see this all the time in the language I am native in, too. Thanks for an input. Let's queue this patch, then.
diff --git a/Documentation/technical/sparse-checkout.txt b/Documentation/technical/sparse-checkout.txt index fa0d01cbda..d968659354 100644 --- a/Documentation/technical/sparse-checkout.txt +++ b/Documentation/technical/sparse-checkout.txt @@ -287,7 +287,7 @@ everything behaves like a dense checkout with a few exceptions (e.g. branch checkouts and switches write fewer things, knowing the VFS will lazily write the rest on an as-needed basis). -Since there is no publically available VFS-related code for folks to try, +Since there is no publicly available VFS-related code for folks to try, the number of folks who can test such a usecase is limited. The primary reason to note the Behavior C usecase is that as we fix things
Fix a typo in documentation. Signed-off-by: Andrew Kreimer <algonell@gmail.com> --- Documentation/technical/sparse-checkout.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)