Re: Copyright information in source files

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>
Cc: vignesh C <vignesh21(at)gmail(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-24 15:14:19
Message-ID: 16733.1574608459@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-11-24 15:25:39 Re: LISTEN/NOTIFY testing woes
Previous Message David Steele 2019-11-24 14:38:09 Re: backup manifests