Date: Thu, 1 Aug 2019 23:01:59 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael@paquier.xyz>,
	Sehrope Sarkuni <sehrope@jackdb.com>,
	Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Fix typos
Message-ID: <20190802030159.GA29394@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <838.1564712294@sss.pgh.pa.us>
User-Agent: Mutt/1.9.4 (2018-02-28)
Precedence: bulk

On 2019-Aug-01, Tom Lane wrote:

> It's British vs. American spelling.  For the most part, Postgres
> follows American spelling, but there's the odd Briticism here and
> there.  I'm not sure whether it's worth trying to standardize.
> I think the most recent opinion on this was Munro's:
> 
> https://www.postgresql.org/message-id/CA+hUKGJz-pdMgWXroiwvN-aeG4-AjdWj3gWdQKOSa8g65spdVw@mail.gmail.com

I think slight variations don't really detract from the value of the
product, and consider the odd variation a reminder of the diversity of
the project.  I don't suggest that we purposefully introduce spelling
variations, or that we refrain from fixing ones that appear in code
we're changing, but I don't see the point in changing a line for the
sole reason of standardising the spelling of a word.

That said, I'm not a native English speaker.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services