Thread

Commits

  1. Doc: add pre-branch task to run src/tools/copyright.pl.

  2. Fix incorrect year in some copyright notices

  3. ecpg: Add missing newline in meson.build

  1. Suggestion: Update Copyright Year to 2025 in Recently Added Files

    Shaik Mohammad Mujeeb <mujeeb.sk.dev@gmail.com> — 2025-05-18T06:39:23Z

    Hi Hackers,
    
    I noticed that in the recently added files (waiteventset.h and
    pg_localeconv_r.c), the copyright notice still mentions the year range as
    1996-2024.
    
    Just wanted to check - should this be updated to reflect 1996-2025 instead?
    
    Thanks & Regards,
    Shaik Mohammad Mujeeb
    Member Technical Staff
    Zoho Corp
    
  2. Re: Suggestion: Update Copyright Year to 2025 in Recently Added Files

    Michael Paquier <michael@paquier.xyz> — 2025-05-18T23:48:00Z

    On Sun, May 18, 2025 at 12:09:23PM +0530, Shaik Mohammad Mujeeb wrote:
    > I noticed that in the recently added files (waiteventset.h and
    > pg_localeconv_r.c), the copyright notice still mentions the year range as
    > 1996-2024.
    > 
    > Just wanted to check - should this be updated to reflect 1996-2025 instead?
    
    This process is automated by src/tools/copyright.pl on a yearly-basis,
    but it is possible that holes appear when some code gets committed
    that predates the new year.
    
    The tool is also pointing at 001_sepgsql.pl and gin_tuple.h.  Will
    fix, thanks for the report.
    --
    Michael
    
  3. Re: Suggestion: Update Copyright Year to 2025 in Recently Added Files

    Tom Lane <tgl@sss.pgh.pa.us> — 2025-05-19T03:34:07Z

    Michael Paquier <michael@paquier.xyz> writes:
    > On Sun, May 18, 2025 at 12:09:23PM +0530, Shaik Mohammad Mujeeb wrote:
    >> Just wanted to check - should this be updated to reflect 1996-2025 instead?
    
    > This process is automated by src/tools/copyright.pl on a yearly-basis,
    > but it is possible that holes appear when some code gets committed
    > that predates the new year.
    
    I had the idea that this was part of our pre-branch checklist,
    but it was not mentioned there.  I added it.
    
    			regards, tom lane
    
    
    
    
  4. Re: Suggestion: Update Copyright Year to 2025 in Recently Added Files

    Michael Paquier <michael@paquier.xyz> — 2025-05-19T06:36:31Z

    On Sun, May 18, 2025 at 11:34:07PM -0400, Tom Lane wrote:
    > I had the idea that this was part of our pre-branch checklist,
    > but it was not mentioned there.  I added it.
    
    Good idea.  Thanks.
    --
    Michael
    
  5. Re: Suggestion: Update Copyright Year to 2025 in Recently Added Files

    Bruce Momjian <bruce@momjian.us> — 2025-05-20T15:47:56Z

    On Sun, May 18, 2025 at 11:34:07PM -0400, Tom Lane wrote:
    > Michael Paquier <michael@paquier.xyz> writes:
    > > On Sun, May 18, 2025 at 12:09:23PM +0530, Shaik Mohammad Mujeeb wrote:
    > >> Just wanted to check - should this be updated to reflect 1996-2025 instead?
    > 
    > > This process is automated by src/tools/copyright.pl on a yearly-basis,
    > > but it is possible that holes appear when some code gets committed
    > > that predates the new year.
    > 
    > I had the idea that this was part of our pre-branch checklist,
    > but it was not mentioned there.  I added it.
    
    I only run it in early January of each year.
    
    -- 
      Bruce Momjian  <bruce@momjian.us>        https://momjian.us
      EDB                                      https://enterprisedb.com
    
      Do not let urgent matters crowd out time for investment in the future.