| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
| Cc: | Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Year of first commit |
| Date: | 2025-01-21 18:27:15 |
| Message-ID: | 3365142.1737484035@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> writes:
> Why is this important ? Well, if that file has a 2014-2025, I can know how
> old it is, more or less which version was included, etc
> Additionally, I see all of you adding or removing a single letter to
> sources, why not adjust those years on header files ?
Our git history is a far more reliable guide to how long a specific
file has existed or which versions included it. The copyright notices
exist only for legal reasons. In my layman's understanding of
copyright law, it's better to take a maximalist approach to labeling
the copyright years. That's why, for example, we advance the end
date on every file every year, even if it receives no other changes
that year.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2025-01-21 18:28:43 | Re: New feature request for adding session information to PostgreSQL transaction log |
| Previous Message | Andrey M. Borodin | 2025-01-21 18:24:12 | Re: Compression of bigger WAL records |