Re: moving basebackup code to its own directory

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, David Steele <david(at)pgmasters(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: moving basebackup code to its own directory
Date: 2022-08-10 14:08:02
Message-ID: CA+Tgmobs7EXH3dFKUKOj70PDWd4c9uqpg+DAVVf6ieskB9E6Lg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 9, 2022 at 3:28 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Aug 9, 2022 at 2:40 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> > It looks like this updates the header comments in the .h files but not the .c
> > files.
> >
> > Personally, I find these to be silly boilerplate ..
>
> Here is a version with some updates to the silly boilerplate.

If there are no further comments on this I will go ahead and commit it.

David Steele voted for back-patching this on the grounds that it would
make future back-patching easier, which is an argument that seems to
me to have some merit, although on the other hand, we are already into
August so it's quite late in the day. Anyone else want to vote?

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-08-10 14:25:03 Re: moving basebackup code to its own directory
Previous Message Alvaro Herrera 2022-08-10 14:03:00 designated initializers