Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tkUw1-004XQH-Vj for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Feb 2025 21:15:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tkUw0-000z25-Fy for pgsql-hackers@arkaria.postgresql.org; Tue, 18 Feb 2025 21:15:16 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tkUw0-000z1x-6g for pgsql-hackers@lists.postgresql.org; Tue, 18 Feb 2025 21:15:16 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tkUvx-001dIa-1t for pgsql-hackers@lists.postgresql.org; Tue, 18 Feb 2025 21:15:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=Yhh3mEm7MH9xkDSTUqcA8xFQ7+MdYBBdERfA6yyWYtE=; b=kSI1bAhLjl+yEGifQSxWmMlWfK +oNGoe7jwk0ALECWSKAwQ27w1pgRRAk1jBr1cTLwxVfE/k76QsUNozujjPdUFEHctkUy4ubDNP29c dWBdurnTLMEIWl3gl2XBlahNZuvOlHqpFg8ZRs1cQI2AXTn5uI1g4v2P81ckupm8/tZH9Idk9XEGP u2oD3W+adL1t5d5iIkpU7JZ3m+n6AQSsVY8H2jiFHTEkUrMpWA/95rwrE4T4zBoA1T0olKIleIq8B R7PZhmjLvKa+zI7npm7DkKzyvX45eB/SUslUKQl7m9SSNCX56XX/V9nQCwNHAIbMoa1kspSOmPlMo Ijml8Htg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1tkUvv-008cX2-0U; Tue, 18 Feb 2025 16:15:11 -0500 Date: Tue, 18 Feb 2025 16:15:11 -0500 From: Bruce Momjian To: =?utf-8?Q?=C3=81lvaro?= Herrera Cc: Jelte Fennema-Nio , PostgreSQL Hackers , Jacob Brazeal Subject: Re: Commitfest app release on Feb 17 with many improvements Message-ID: References: <202502041627.zw6lvwjtjlu4@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <202502041627.zw6lvwjtjlu4@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.