Re: Copyright information in source files

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>, 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-26 16:31:41
Message-ID: CALDaNm2nNeERCEq9ESOPU4MyK9ZVKSYitzokZWHQZ0=pyZ5q1A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Nov 24, 2019 at 8:44 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> John Naylor <john(dot)naylor(at)2ndquadrant(dot)com> writes:
> > 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?
>
> Good question.
>
> I was wondering about something even simpler: is there a reason to
> have per-file copyright notices at all? Why isn't it good enough
> to have one copyright notice at the top of the tree?
>
> Actual legal advice might be a good thing to have here ...

+1 for having single copyright notice at the top of the tree.
What about file header, should we have anything at all?

Regards,
Vignesh
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-11-26 18:25:18 Re: CVE-2017-7484-induced bugs, or, btree cmp functions are not leakproof?
Previous Message Tom Lane 2019-11-26 15:49:11 Re: ERROR: attribute number 6 exceeds number of columns 5