Re: make update-po@master stops at pg_upgrade

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: make update-po@master stops at pg_upgrade
Date: 2022-08-08 16:08:09
Message-ID: 20220808160809.wzzztbdjsydwgqsh@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2022-Jul-28, Tom Lane wrote:

> Thanks for testing it. I think the only remaining concern is
> Peter's objection that $(wildcard) might pick up random junk files
> that end in ".c". That's true, but the backend's nls.mk also
> picks up everything matching "*.c" (over the whole backend tree,
> not just one directory!),

Now that I did the translation chores again after a few years I am
reminded of a point about this argument: in reality, few people ever
run this recipe manually (I know I never do), because it's easier to
grab the already-merged files from the NLS website. It all happens
mechanically and there's nobody leaving random junnk files.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"El que vive para el futuro es un iluso, y el que vive para el pasado,
un imbécil" (Luis Adler, "Los tripulantes de la noche")

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2022-08-08 16:17:37 Re: Remaining case where reltuples can become distorted across multiple VACUUM operations
Previous Message Andres Freund 2022-08-08 16:02:04 Re: bug on log generation ?