public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Álvaro Herrera <[email protected]>
Cc: Jelte Fennema-Nio <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: Jacob Brazeal <[email protected]>
Subject: Re: Commitfest app release on Feb 17 with many improvements
Date: Tue, 18 Feb 2025 16:15:11 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAGECzQTbHhaZMY-=Y=OGMU_jik4MqCfsc7rDf6AnT=Aq-B6cZA@mail.gmail.com>
	<[email protected]>

On Tue, Feb  4, 2025 at 05:27:18PM +0100, Álvaro Herrera wrote:
> 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.

Looking at the live version, I can sort the "Stats" column from smallest
to largest, but not from largest to smallest.  Is this intended?

-- 
  Bruce Momjian  <[email protected]>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.

view thread (34+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Commitfest app release on Feb 17 with many improvements
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox