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