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

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tender Wang <tndrwang(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH v1] Fixed a spelling error in the comments in gininsert.c
Date: 2025-12-22 00:47:14
Message-ID: AEE078E8-2B9F-4121-AAB0-A672F8241B78@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Dec 22, 2025, at 06:22, Michael Paquier <michael(at)paquier(dot)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/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin K Biju 2025-12-22 02:30:00 Allowing ALTER COLUMN TYPE for columns in publication column lists
Previous Message Thomas Munro 2025-12-22 00:24:43 Re: [PATCH] O_CLOEXEC not honored on Windows - handle inheritance chain