From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Brainstorming features for issues.guix.gnu.org Date: Mon, 30 Mar 2020 10:07:35 +0200 Message-ID: <87y2riw9jf.fsf@elephly.net> References: <87mu83xzzr.fsf@elephly.net> <87blofpii8.fsf@asu.edu> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57582) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jIpSS-0002M8-Bh for guix-devel@gnu.org; Mon, 30 Mar 2020 04:07:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jIpSR-0000fa-AH for guix-devel@gnu.org; Mon, 30 Mar 2020 04:07:44 -0400 Received: from sender4-of-o54.zoho.com ([136.143.188.54]:21499) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jIpSQ-0000eJ-Tt for guix-devel@gnu.org; Mon, 30 Mar 2020 04:07:43 -0400 In-reply-to: <87blofpii8.fsf@asu.edu> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: John Soo Cc: guix-devel@gnu.org John Soo writes: > It can be hard to review a patchset with multiple revisions > (particularly when sent as attachments). I agree. > It is hard to find how patchsets differ - let alone where > revisions start and end. Do you have an idea how to improve this? Should we use, for example, the message subject to detect revisions? (E.g. [PATCH 3/3] will indicate that the end of the patch set has been reached.) How would we indicate different patch sets visually? Should there be links somewhere to jump to patch sets? -- Ricardo