| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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-10 01:19:09 |
| Message-ID: | 54B07E0D.7010308@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/6/15, 6:15 PM, Tom Lane wrote:
> Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
>> On 1/6/15, 3:30 PM, Stefan Kaltenbrunner wrote:
>>> 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
>
> Unless either of you is a copyright lawyer, your opinion on whether that's
> sufficient is of zero relevance.
No, but a friend's dad is. I could probably get his opinion on it if that would be helpful.
> Personally I think it's just fine if we have some mechanism that forces
> text files to have trailing newlines ;-)
Which is what I was suggesting... ;) AFAIK that would be a matter of installing the appropriate hook on git.postgresql.org.
https://www.google.com/search?q=git+enforce+trailing+newline
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-01-10 01:59:07 | Re: Escaping from blocked send() reprised. |
| Previous Message | Jim Nasby | 2015-01-10 00:56:45 | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |