Horton

Re: [PATCH v1] Fixed a spelling error in the comments in gininsert.c

Chao Li <li.evan.chao@gmail.com>

View thread
From: Chao Li <li.evan.chao@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Tender Wang <tndrwang@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-12-22T00:47:14Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix another typo in gininsert.c

  2. Fix typos in gininsert.c


> On Dec 22, 2025, at 06:22, Michael Paquier <michael@paquier.xyz> wrote:
> 
> On Sat, Dec 20, 2025 at 08:31:28AM +0800, Chao Li wrote:
>> I found that earlier, but when I checked with
>> https://www.onelook.com/?w=endianess, it has two matches, so I
>> guessed that spelling is acceptable.
> 
> I've always heard only about the spelling with two 'n', the one you
> are pointing at being a redirection to the two-n version as well.
> Additionally, the rest of the tree seems to agree with that:
> $ git grep endianness | wc -l
> 13
> $ git grep endianess | wc -l
> 0
> --
> Michael

I have no objection at all.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/