From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Soo Subject: Re: Brainstorming features for issues.guix.gnu.org Date: Mon, 30 Mar 2020 14:48:50 -0700 Message-ID: <87h7y5v7i5.fsf@asu.edu> References: <87mu83xzzr.fsf@elephly.net> <87blofpii8.fsf@asu.edu> <87y2riw9jf.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:46213) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJ2HB-0006vP-Ea for guix-devel@gnu.org; Mon, 30 Mar 2020 17:48:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jJ2H9-0005f7-CC for guix-devel@gnu.org; Mon, 30 Mar 2020 17:48:56 -0400 Received: from mail-ot1-x334.google.com ([2607:f8b0:4864:20::334]:40937) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jJ2H7-0005eI-Vx for guix-devel@gnu.org; Mon, 30 Mar 2020 17:48:55 -0400 Received: by mail-ot1-x334.google.com with SMTP id r19so14013926otn.7 for ; Mon, 30 Mar 2020 14:48:53 -0700 (PDT) In-Reply-To: <87y2riw9jf.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 30 Mar 2020 10:07:35 +0200") 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: Ricardo Wurmus Cc: guix-devel@gnu.org Ricardo Wurmus writes: >> 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? Hmm. I don't know if I have a good answer yet. I think I like the debbugs threaded view. Here are a couple ideas: * Allow expansion/collapse of diffs * Provide a thread view and a view of just one patchset (maybe computed via [PATCH 3/3] or by attachments as you mention) * Provide an interdiff view between revisions * Only show the most recent patchset like some large commercial products I like the thread view idea since this is an email workflow, afterall. It has been improving a lot and I am already using it a lot more now that it has its own database. John