Re: Fixed redundant i18n strings in json - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Fixed redundant i18n strings in json
Date
Msg-id CA+TgmoY6gSoNtrRX3_yRQgVa639PVBUmY+ygYdUL9X7DgHcY4A@mail.gmail.com
Whole thread Raw
In response to Re: Fixed redundant i18n strings in json  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
Responses Re: Fixed redundant i18n strings in json
Re: Fixed redundant i18n strings in json
List pgsql-hackers
On Sat, Aug 2, 2014 at 9:15 AM, Daniele Varrazzo
<daniele.varrazzo@gmail.com> wrote:
> I'd definitely replace /arg/argument/. Furthermore I'd avoid the form
> "argument 1: something is wrong": the string is likely to end up in
> sentences with other colons so I'd rather use "something is wrong at
> argument 1".
>
> Is the patch attached better?

Looks OK to me.  I thought someone else might comment, but since no
one has, committed.

(As a note for the future, you forgot to update the regression test
outputs; I took care of that before committing.)

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Spinlocks and compiler/memory barriers
Next
From: Jerry Sievers
Date:
Subject: Append to a GUC parameter ?