Date: Mon, 14 Feb 2022 18:22:33 -0300
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>,
	Thomas Munro <tmunro@postgresql.org>,
	pgsql-committers <pgsql-committers@lists.postgresql.org>
Subject: Re: pgsql: Track LLVM 15 changes.
Message-ID: <202202142122.eqz4mu2ecfes@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CA+hUKGLqengPszjoQeD_7nmHsjGZS380+ymke-Fm=nNGMEQuhw@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202202142122.eqz4mu2ecfes%40alvherre.pgsql>
Precedence: bulk

On 2022-Feb-15, Thomas Munro wrote:

> My general plan for this stuff is to try to do just one back-patch for
> each LLVM release, with all the changes in it, to reduce commit churn.
> Hence commit messages that say "Track LLVM X ..." so that it's easy to
> find all the changes for X around the time of X's release.  In other
> words I'll probably do the 14 back-patch next month, so our May
> releases will compile and work against LLVM 14, due out in March.

In this case, maybe you should get this task listed in RELEASE_CHANGES.

-- 
Álvaro Herrera