| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| 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>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Updating copyright notices to 2015 for PGDG |
| Date: | 2015-01-06 23:56:26 |
| Message-ID: | CAB7nPqRMRpfQLQJQ+NAPAePsR5mknRmENabp6LPimhPrMwG=ww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 7, 2015 at 8:48 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> 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
>
> Also, now that we're on git it wouldn't be that hard to add commit hooks
> that prevent (or maybe even fix) trailing LF. If this is somethin pg_indent
> or other tools would do anyway ISTM it'd be nice to use a hook that fixes it
> because it would cut down on the size of pg_indent diffs.
... And increase the size of vanilla commits if you do it in the same
commit, or make the git history less readable if you fix them as a
separate commit. It is better IMO to keep the cleanup work in a single
huge commit.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-01-06 23:59:42 | Re: XLOG_PARAMETER_CHANGE handling of wal_log_hints |
| Previous Message | Andrew Dunstan | 2015-01-06 23:54:59 | Re: pg_rewind in contrib |