Re: BUG #13589: content error

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, barnettluisa(at)gmail(dot)com, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13589: content error
Date: 2015-08-26 07:55:59
Message-ID: CAEepm=2tfJyO-9tUw3h5tvPbJ=FM3Q=1X61ddKtLGRf6kFCQPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Aug 26, 2015 at 10:19 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> As mentioned upthread, constructive criticism in the form of a patch
> might serve to move the discussion forward.

Here is a patch showing around 45 suggested changes to get the ball
rolling. Mostly "he or she", but sometimes other wording, and in one
case I took a few liberties and introduced <literal>name</> to stand
in for database objects instead of pronouns which I hope doesn't read
too clumsily or change the meaning. I didn't cover the release notes.

A big +1 from me for changing this (unintentionally) unwelcoming
language generally, whatever the new wording.

--
Thomas Munro
http://www.enterprisedb.com

Attachment Content-Type Size
language.patch application/octet-stream 18.3 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message d.stelzner 2015-08-26 10:36:44 BUG #13591: Boolean type presented as varchar by ODBC
Previous Message Robert Mu 2015-08-26 06:50:01 Re: Issue when using ltree