Date: Tue, 9 Feb 2016 08:24:53 +0100 (CET)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Michael Paquier <michael.paquier@gmail.com>
cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Subject: Re: pgbench stats per script & other stuff
In-Reply-To: 
 <CAB7nPqQ_pswd1D89QdGfs+qWHp5YPQiA9MCDY8t7AkvxtED5xQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.10.1602090814590.30372@sto>
References: <20160204095806.GA220429@alvherre.pgsql>
 <alpine.DEB.2.10.1602041520590.20461@sto>
 <CAB7nPqSvqcbCaK2xG7otB3qSopqrkoMmOMRw=PCjs_-VQjpfZw@mail.gmail.com>
 <alpine.DEB.2.10.1602081953560.22398@sto>
 <CAB7nPqQ_pswd1D89QdGfs+qWHp5YPQiA9MCDY8t7AkvxtED5xQ@mail.gmail.com>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org


Hi Michaël,

>> Attached 19-d and 19-e.
>
> +/* return builtin script "name", or fail if not found */
> builtin does not sound like correct English to me, but built-in is.

I notice that "man bash" uses "builtin" extensively, so I think it is okay 
like that, but I would be fine as well with "built-in".

I suggest to let it as is unless some native speaker really requires 
"built-in", in which case there would be many places to update, so that 
would be another orthographic-oriented patch:-)

-- 
Fabien.
-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers