On Thu, Nov 20, 2025 at 11:42:39AM +0100, Álvaro Herrera wrote:
> On 2025-Nov-20, David Rowley wrote:
>
> > Maybe you'd be better with git ls-files if you only want just what's
> > in the repo. Something like:
> >
> > for b in "REL8_0_0" "REL8_1_0" "REL8_2_0" "REL8_3_0" "REL8_4_0"
> > "REL9_0_0" "REL9_1_0" "REL9_2_0" "REL9_3_0" "REL9_4_0" "REL9_5_0"
> > "REL9_6_0" "REL_10_0" "REL_11_0" "REL_12_0" "REL_13_0" "REL_14_0"
> > "REL_15_0" "REL_16_0" "REL_17_0" "REL_18_0" "master"; do git checkout
> > -f $b > /dev/null 2>&1 && echo -n "$b " && git ls-files -- '*.[chyl]'
> > | xargs cat | wc -l; done
>
> Maybe this should also consider .pl and .pm files ... we now have almost
> 90k lines of Perl code in branch master:
>
> I perhan: master 0 0$ git ls-files -- '*.pl' | xargs cat | wc -l
> 77234
> C perhan: master 0 0 0$ git ls-files -- '*.pm' | xargs cat | wc -l
> 10386
Well, I am trying to count only the code that is part of a cluster
install, or optionally an install for extensions. Aren't most of the
Perl files testing? Not sure we want to count that.
--
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.
