Re: [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation. - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.
Date
Msg-id CAEepm=0=VFjCcRRSBf9BFyAhME0vJBJQgoc9EvhEYLBd84xCLA@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [COMMITTERS] pgsql: Copy-editing for contrib/pg_visibility documentation.  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Mon, Oct 3, 2016 at 1:36 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Sat, Oct 1, 2016 at 3:33 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Copy-editing for contrib/pg_visibility documentation.
>>
>> Add omitted names for some function parameters.
>> Fix some minor grammatical issues.
>
> Why do you keep insisting on changing case where I've written "which"
> to instead say "that" in situations where AFAIK either is perfectly
> correct?  I find such changes at best neutral, and in some cases
> worse.

'Which' looks OK to me too here, but I speak some kind of British
English, and it looks like at least some writers of formal American
English prefer 'that' here:

* http://www.chicagomanualofstyle.org/qanda/data/faq/topics/Whichvs.That.html?old=Whichvs.That01.html
* https://en.oxforddictionaries.com/usage/that-or-which

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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [PATCH] add option to pg_dumpall to exclude tables from the dump
Next
From: Michael Paquier
Date:
Subject: Re: "Re: Question about grant create on database and pg_dump/pg_dumpall