Re: Commitfest app release on Feb 17 with many improvements - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: Commitfest app release on Feb 17 with many improvements
Date
Msg-id 202502041627.zw6lvwjtjlu4@alvherre.pgsql
Whole thread Raw
In response to Commitfest app release on Feb 17 with many improvements  (Jelte Fennema-Nio <postgres@jeltef.nl>)
Responses Re: Commitfest app release on Feb 17 with many improvements
List pgsql-hackers
On 2025-Jan-31, Jelte Fennema-Nio wrote:

> 3. Showing total additions/deletions of the most recent patchset on
> patch and commitfest pages
> 4. Showing additions/deletions of the first patch of the most recent
> patchset on the patch page
> 5. Showing the version and number of patches of the most recent
> patchset on the patch page

I think this has potential for excessive clutter.  I propose that, if
we're going to have a column with addition/deletions, we have two
things:

1. the total number of addition and deletions in the whole patch
   series, for the last patchset version posted.  This would be shown in
   the column.
2. a per-patch breakdown of the number of addition and deletions for the
   last patchset version posted, one line per patch.  This would appear
   in a tooltip on the column for the totals, to avoid interface
   clutter.

> 10. Allow sorting patches by total additions/deletions (added together
> for total lines changed)

Seems reasonable, though I don't see much of an use-case for this.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Postgres is bloatware by design: it was built to house
 PhD theses." (Joey Hellerstein, SIGMOD annual conference 2002)



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Better title output for psql \dt \di etc. commands
Next
From: Ilyasov Ian
Date:
Subject: RE: SIGSEGV, FPE fix in pg_controldata