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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
