Re: pgsql: Track LLVM 15 changes.

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Thomas Munro <tmunro(at)postgresql(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Track LLVM 15 changes.
Date: 2022-02-14 21:22:33
Message-ID: 202202142122.eqz4mu2ecfes@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2022-02-14 22:15:24 Re: pgsql: Track LLVM 15 changes.
Previous Message Peter Eisentraut 2022-02-14 21:18:04 pgsql: Move scanint8() to numutils.c