| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Fixup a few 2023 copyright years |
| Date: | 2024-04-09 02:21:42 |
| Message-ID: | CAApHDvr5egyW3FmHbAg-Uq2p_Aizwco1Zjs6Vbq18KqN64-hRA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Attached is a patch which adjusts the copyright years of 2023 that
have crept in this year from patches that were written last year and
committed without adjusting this to 2024.
The patch isn't produced by src/tools/copyright.pl as that'll
transform files which are new and only contain "2023" to become
"2023-2024", which I don't believe is what we want in this case.
No other matches aside from .po files from:
git grep -e "Copyright" --and --not -e "2024" --and -e "PostgreSQL
Global Development Group"
Should we do this and is this a good time to?
David
| Attachment | Content-Type | Size |
|---|---|---|
| fix_wrong_copyright_year.patch | text/plain | 5.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-04-09 02:27:36 | Re: Fixup some StringInfo usages |
| Previous Message | Tom Lane | 2024-04-09 02:12:16 | Re: post-freeze damage control |