Re: Fixup a few 2023 copyright years - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Fixup a few 2023 copyright years
Date
Msg-id ZhS1N8sSTmvTDmTS@paquier.xyz
Whole thread Raw
In response to Re: Fixup a few 2023 copyright years  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fixup a few 2023 copyright years
List pgsql-hackers
On Mon, Apr 08, 2024 at 10:36:41PM -0400, Tom Lane wrote:
> We *should* do this sometime before branching v17, but I'm not
> in any hurry.  My thought here is that some of these late changes
> might end up getting reverted, in which case touching those files
> would add a bit more complexity to the revert.  We can do this
> sort of mechanical cleanup after the probability of reversion has
> declined a bit.
>
> (On the same logic, I'm resisting the temptation to do a tree-wide
> pgindent right away.  Yeah, the tree is indent-clean according to
> the current contents of src/tools/pgindent/typedefs.list, but that
> hasn't been maintained with great accuracy, so we'll need an
> update and then a pgindent run at some point.)

The perl code in the tree has gathered dust, on the contrary ;)

I would suggest to also wait until we're clearer with the situation
for all these mechanical changes, which I suspect is going to take 1~2
weeks at least.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Security lessons from liblzma
Next
From: Michael Paquier
Date:
Subject: Re: Weird test mixup