From: | vignesh C <vignesh21(at)gmail(dot)com> |
---|---|
To: | John Naylor <john(dot)naylor(at)2ndquadrant(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 09:51:03 |
Message-ID: | CALDaNm0H7Oyo0u5Y5y25JMM39mX2XR+p3kLQ23U2D_+PgOWjiw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Nov 24, 2019 at 7:24 AM John Naylor <john(dot)naylor(at)2ndquadrant(dot)com> wrote:
>
> 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?
>
That idea sounds good to me. Also that way no need to update the year
every year or can we mention using current to indicate the latest
year, something like:
* Copyright (c) 2016-current, PostgreSQL Global Development Group
Regards,
Vignesh
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2019-11-24 10:24:58 | Re: dropdb --force |
Previous Message | Mark Dilger | 2019-11-24 04:50:52 | Re: LISTEN/NOTIFY testing woes |