| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Copyright in partition.h and partition.c |
| Date: | 2017-09-05 07:08:22 |
| Message-ID: | a4f8c0c0-e931-6d03-758f-52f400122e05@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017/09/05 15:48, Etsuro Fujita wrote:
> Here is the copyright in partition.h:
>
> * Copyright (c) 2007-2017, PostgreSQL Global Development Group
>
> I think it's reasonable that that matches the copyright in partition.c,
> but partition.c has:
>
> * Portions Copyright (c) 1996-2017, PostgreSQL Global Development Group
> * Portions Copyright (c) 1994, Regents of the University of California
>
> Is that intentional?
No, it's unintentional. The difference may have resulted from copying
different files to become partition.h and partition.c, respectively.
Maybe, we should change both to say 2016-2017?
I don't know the exact rule for how we determine those years. Is there
some rule in place about that? When I look at execParallel.c, which
supposedly got introduced into the tree recently, I see 1996-2017. OTOH,
the files in contrib/bloom all have 2016-2017.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-09-05 07:24:04 | Re: pgbench: Skipping the creating primary keys after initialization |
| Previous Message | Fabien COELHO | 2017-09-05 07:06:28 | Re: pgbench: Skipping the creating primary keys after initialization |