| From: | John Naylor <john(dot)naylor(at)2ndquadrant(dot)com> |
|---|---|
| To: | vignesh C <vignesh21(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Copyright information in source files |
| Date: | 2019-11-24 01:54:40 |
| Message-ID: | CACPNZCtgBG8AJmk9QZcYrq8Ao+K_chYqwRyvou6mKEdBjqCYag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 23, 2019 at 11:39 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
> * Copyright (c) 2016-2019, PostgreSQL Global Development Group
While we're talking about copyrights, I noticed while researching
something else that the PHP project recently got rid of all the
copyright years from their files, which is one less thing to update
and one less cause of noise in the change log for rarely-changed
files. Is there actually a good reason to update the year?
--
John Naylor https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2019-11-24 04:50:52 | Re: LISTEN/NOTIFY testing woes |
| Previous Message | Steve Singer | 2019-11-24 01:10:51 | Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly |