From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
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:20:59 |
Message-ID: | 634380.1659975659@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> 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.
Hmm, so where does the NLS website get its data?
I'd be all for flushing the recipe altogether if no one uses it.
However, the existence of this thread suggests otherwise.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2022-08-08 16:38:22 | Re: bug on log generation ? |
Previous Message | Tom Lane | 2022-08-08 16:19:22 | Re: bug on log generation ? |