[PATCH] Fix various spelling errors
Hello!
I propose the attached patch to be applied on the 'master' branch of PostgreSQL
to fix various spelling errors.
Most fixes are in comments and have no effect on functionality. Some fixes are
also in variable names but they should be safe to change, as the change is
consistent in all occurrences of the variable.
Otto Kekalainen
Amazon Web Services: https://aws.amazon.com
Attachments:
v1-0001-Fix-various-spelling-errors.patchapplication/octet-stream; name=v1-0001-Fix-various-spelling-errors.patchDownload+27-22
On Mon, Mar 14, 2022 at 11:03:50PM +0000, Kekalainen, Otto wrote:
Hello!
I propose the attached patch to be applied on the 'master' branch of PostgreSQL
to fix various spelling errors.Most fixes are in comments and have no effect on functionality. Some fixes are
also in variable names but they should be safe to change, as the change is
consistent in all occurrences of the variable.
LGTM - I found a few of these myself.
Attached now, in case it's useful to handle them together.
Attachments:
0001-doc-than-than.patchtext/x-diff; charset=us-asciiDownload+2-3
0002-doc-duplicate-words-THE-since-0aa8a01d04c8fe200b7a10.patchtext/x-diff; charset=us-asciiDownload+1-2
0003-remove-duplicate-word.patchtext/x-diff; charset=us-asciiDownload+1-2
0004-doc-database-SYSTEM-since-aa01051418f10afbdfa781b8dc.patchtext/x-diff; charset=us-asciiDownload+1-2
0005-doc-Remove-synchronized-from-no-sync.patchtext/x-diff; charset=us-asciiDownload+1-2
0006-doc-json-log-dc686681e0799b12c40f44f85fc5bfd7fed4e57.patchtext/x-diff; charset=us-asciiDownload+3-4
0007-doc-Logical-decoding-of-sequences-0da92dc530c9251735.patchtext/x-diff; charset=us-asciiDownload+3-4
0008-doc-s-in-local-server-on-local-server-94c49d53402240.patchtext/x-diff; charset=us-asciiDownload+1-2
0009-doc-pg_column_compression-we-say-method-not-algorith.patchtext/x-diff; charset=us-asciiDownload+1-2
0010-comment-typo-consistency.patchtext/x-diff; charset=us-asciiDownload+1-2
0011-comment-typo-since-ff9f111bce24fd9bbca7a20315586de87.patchtext/x-diff; charset=us-asciiDownload+1-2
0012-Remove-extraneous-blank-lines.patchtext/x-diff; charset=us-asciiDownload+0-4
0013-Cluster.pm-since-b34ca595abd697e716ce369ec1b58624bdd.patchtext/x-diff; charset=us-asciiDownload+3-4
0014-f-extended-stats.patchtext/x-diff; charset=us-asciiDownload+3-4
0015-typos-reported-by-codespell.patchtext/x-diff; charset=us-asciiDownload+9-10
0016-Double-spaces.patchtext/x-diff; charset=us-asciiDownload+9-10
0017-comment-spaces.patchtext/x-diff; charset=us-asciiDownload+3-4
On Mon, Mar 14, 2022 at 06:49:07PM -0500, Justin Pryzby wrote:
On Mon, Mar 14, 2022 at 11:03:50PM +0000, Kekalainen, Otto wrote:
I propose the attached patch to be applied on the 'master' branch of PostgreSQL
to fix various spelling errors.Most fixes are in comments and have no effect on functionality. Some fixes are
also in variable names but they should be safe to change, as the change is
consistent in all occurrences of the variable.LGTM - I found a few of these myself.
Attached now, in case it's useful to handle them together.
It is useful to group that together. I have gathered everything that
looked like a typo or a grammar mistake, and applied the fixes.
Thanks!
--
Michael
On 2022-03-14, 19:47, "Michael Paquier" <michael@paquier.xyz> wrote:
It is useful to group that together. I have gathered everything that
looked like a typo or a grammar mistake, and applied the fixes.
That was quick, thanks!
Please next time use `git am` to import the patch so that author and other
commit metadata is kept, or if you apply patches manually then commit with `git
--author` so that original author will be correct in the commit and your name
will be only in the committer field.
This was just a spelling fix so I don't care, but for other people doing more
significant contributions, getting the git authorship and having a PostgreSQL
contribution show up on their Gihub (or Gitlab profile, or in other tools that
read git commits) can be important and maybe the only reward/credit for those
doing open source on their free time.
Again, personally I don't care and I don't need Github credits for this, just
stating as general advice for a better contribution process in the future.
- Otto
"Kekalainen, Otto" <ottoke@amazon.com> writes:
Please next time use `git am` to import the patch so that author and other
commit metadata is kept, or if you apply patches manually then commit with `git
--author` so that original author will be correct in the commit and your name
will be only in the committer field.
This is not our practice. We credit authors in the body of the commit
message, but we don't worry about the git metadata. git is a tool we
happen to be using at the moment, but it doesn't run the project,
and in any case it's far short of being adequate for such a purpose.
What would you do with multiple-author patches, for a start?
regards, tom lane