|From:||Bruce Momjian <bruce(at)momjian(dot)us>|
|To:||Magnus Hagander <magnus(at)hagander(dot)net>|
|Cc:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>|
|Subject:||Re: mkid reference|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Tue, Jan 26, 2021 at 10:19:44PM +0100, Magnus Hagander wrote:
> On Mon, Jan 25, 2021 at 4:40 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > On Sun, Jan 24, 2021 at 02:20:58PM +0100, Magnus Hagander wrote:
> > > While at it, what point is "codelines" adding?
> > That is the script I use to generate code line counts when comparing
> > releases. I thought it should be in the tree so others can reproduce my
> > numbers.
> Not that it particularly matters to keep it, but wouldn't something
> like cloc give a much better number?
Yes, we could, but we didn't really have any criteria on exactly what to
count, so I just counted physical lines.
The usefulness of a cup is in its emptiness, Bruce Lee
|Next Message||Tomas Vondra||2021-01-26 22:59:05||Re: WIP: BRIN multi-range indexes|
|Previous Message||Bruce Momjian||2021-01-26 22:53:01||Re: Key management with tests|