From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Rowley <dgrowleyml@gmail.com>
Cc: David Rowley <drowley@postgresql.org>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix list_copy_head() with empty Lists
Date: Thu, 20 Apr 2023 18:18:48 -0400
Message-ID: <3227682.1682029128@sss.pgh.pa.us> (raw)
In-Reply-To: <CAApHDvq1Lz9DSiBxkK_pgv1ky5V8L7gGkbto1HNgEpLyKtYS8w@mail.gmail.com>
References: <E1ppGOE-003u13-4o@gemulon.postgresql.org>
<3129478.1681997309@sss.pgh.pa.us>
<CAApHDvq1Lz9DSiBxkK_pgv1ky5V8L7gGkbto1HNgEpLyKtYS8w@mail.gmail.com>
David Rowley <dgrowleyml@gmail.com> writes:
> Doh :-( Thanks for alerting me. I've just applied the patch to REL_15_STABLE.
> I kept the same commit message as master, which I think was the
> correct thing to do, despite it containing information that wasn't
> true. I know the script used to assist release note creation goes on
> commit messages to determine which commits went into which branches.
Yeah, that's definitely easier for release notes, so thanks.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, dgrowleyml@gmail.com, drowley@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix list_copy_head() with empty Lists
In-Reply-To: <3227682.1682029128@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox