From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
cc: Hugh Ranalli <hugh@whtc.ca>, Michael Paquier <michael@paquier.xyz>,
        Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
        thomas.munro@enterprisedb.com,
 Daniel Verite <daniel@manitou-mail.org>,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15548: Unaccent does not remove combining diacritical
 characters
In-reply-to: <201901031819.hi4hjki2pzr5@alvherre.pgsql>
References: <201901031819.hi4hjki2pzr5@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@2ndquadrant.com>
	message dated "Thu, 03 Jan 2019 15:19:58 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23618.1546539744.1@sss.pgh.pa.us>
Date: Thu, 03 Jan 2019 13:22:24 -0500
Message-ID: <23619.1546539744@sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> I think the point is that if the committee updates with a further
> version of the file, how do you find the new version?  We need a URL
> that's one step removed from the final file, so that we can see if we
> need to update it.  Maybe we can provide both URLs for convenience.

+1.  Could be phrased along the lines of "documents are at URL1,
currently synced with URL2" so that it's clear that URL2 should
be updated when we re-sync with a newer release.

			regards, tom lane