Feedback-ID: ie0a040ee:Fastmail
Message-ID: <b8db6ace-f73f-4ad6-93a2-47ab2cfb63a4@eisentraut.org>
Date: Mon, 2 Mar 2026 08:29:52 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Unicode update and some tooling improvements
To: Chao Li <li.evan.chao@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
References: <2a668979-ed92-49a3-abf9-a3ec2d460ec2@eisentraut.org>
 <906DA1A8-73FD-4BE5-AD82-80C871602BAE@gmail.com>
Content-Language: en-US
From: Peter Eisentraut <peter@eisentraut.org>
In-Reply-To: <906DA1A8-73FD-4BE5-AD82-80C871602BAE@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/b8db6ace-f73f-4ad6-93a2-47ab2cfb63a4%40eisentraut.org>
Precedence: bulk

On 27.02.26 03:50, Chao Li wrote:
> Only a small comment on 0003:
> ```
>     # Meson 0.57.0 and 0.57.1 are buggy, therefore >=0.57.2.
> -  meson_version: '>=0.57.2',
> +  # FIXME: update comment
> +  meson_version: '>=0.58',
> ```
> 
> Why leaves a FIXME instead of just updating the comment? I saw the installation.sgml doc has been updated.

It wasn't meant to be committed that way.  I just didn't want to spend 
the time crafting a comment before it was generally agreed to proceed in 
this way that required a meson version update.