From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, David Fetter <david(at)fetter(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Updating copyright notices to 2015 for PGDG |
Date: | 2015-01-06 23:12:18 |
Message-ID: | 20150106231218.GT1457@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stefan Kaltenbrunner wrote:
> On 01/06/2015 10:12 PM, Alvaro Herrera wrote:
> > This makes me wonder however how wise it is to update the copyright
> > notices in every single file in the repo. Why do we need this? Why not
> > abolish the practice and live forever with most files having copyright
> > 2015? (Only new files would have newer years in their copyright
> > notices, I guess.) Does this provide us with any kind of protection,
> > and if so against what, and how does it protect us? Since we have a
> > very clean git history which shows us the exact provenance of every
> > single line of source code, and we have excellent mail archives that
> > show where each line came from for all development in the last decade,
> > this single line of (C) boilerplate in each file seems completely
> > pointless.
>
> I dont know why it is really needed but maybe for the files that have
> identical copyrights one could simple reference to the COPYRIGHT file we
> already have in the tree?
+1 to that, but I would +2 a script that just did
g/Copyright Regents of Fooniversity/d
etc.
Abhijit et al will probably hate me for referencing this, but here it
goes anyway:
http://toroid.org/ams/etc/updating-copyright-notices
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2015-01-06 23:13:52 | Re: Re: Patch to add functionality to specify ORDER BY in CREATE FUNCTION for SRFs |
Previous Message | Jim Nasby | 2015-01-06 23:05:33 | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |