Re: 10% drop in code line count in PG 17

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: 10% drop in code line count in PG 17
Date: 2025-11-19 22:00:31
Message-ID: 202511192159.n422xy47gok2@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-Nov-19, Tom Lane wrote:

> > No, I just followed the shell comment I wrote above the 'find' command
> > shown above:
>
> > # This script is used to compute the total number of "C" lines in the
> > # release This should be run from the top of the Git tree after a 'make
> > # distclean'
>
> > And that tree has been built many times. Should I change my procedure?
>
> Does "git status --ignored" show any leftover junk files?

Maybe it'd be better to use `git ls-files` to create the list of files.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"But static content is just dynamic content that isn't moving!"
http://smylers.hates-software.com/2007/08/15/fe244d0c.html

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2025-11-19 22:03:59 Re: Consistently use the XLogRecPtrIsInvalid() macro
Previous Message Bruce Momjian 2025-11-19 21:58:15 Re: 10% drop in code line count in PG 17