Re: Fixup a few 2023 copyright years

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fixup a few 2023 copyright years
Date: 2024-04-09 03:25:43
Message-ID: ZhS1N8sSTmvTDmTS@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-04-09 03:41:57 Re: Weird test mixup
Previous Message Bruce Momjian 2024-04-09 02:57:27 Re: Security lessons from liblzma