Re: Fixup a few 2023 copyright years
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Rowley <dgrowleyml@gmail.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2024-04-09T03:25:43Z
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
Commits
-
Fix incorrect year in some copyright notices added this year
- 8cb653b2457c 17.0 landed