Re: moving basebackup code to its own directory - Mailing list pgsql-hackers

From Robert Haas
Subject Re: moving basebackup code to its own directory
Date
Msg-id CA+Tgmobs7EXH3dFKUKOj70PDWd4c9uqpg+DAVVf6ieskB9E6Lg@mail.gmail.com
Whole thread Raw
In response to Re: moving basebackup code to its own directory  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: moving basebackup code to its own directory
Re: moving basebackup code to its own directory
Re: moving basebackup code to its own directory
List pgsql-hackers
On Tue, Aug 9, 2022 at 3:28 PM Robert Haas <robertmhaas@gmail.com> wrote:
> On Tue, Aug 9, 2022 at 2:40 PM Justin Pryzby <pryzby@telsasoft.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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: designated initializers
Next
From: Justin Pryzby
Date:
Subject: Re: moving basebackup code to its own directory