From: John Soo <jsoo1@asu.edu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Brainstorming features for issues.guix.gnu.org
Date: Mon, 30 Mar 2020 14:48:50 -0700 [thread overview]
Message-ID: <87h7y5v7i5.fsf@asu.edu> (raw)
In-Reply-To: <87y2riw9jf.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 30 Mar 2020 10:07:35 +0200")
Ricardo Wurmus <rekado@elephly.net> 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
prev parent reply other threads:[~2020-03-30 21:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 8:49 Brainstorming features for issues.guix.gnu.org Ricardo Wurmus
2020-03-26 9:40 ` Arun Isaac
2020-03-26 9:49 ` Vincent Legoll
2020-03-26 9:46 ` Vincent Legoll
2020-03-26 9:47 ` Pierre Neidhardt
2020-03-26 9:51 ` Vincent Legoll
2020-03-26 10:29 ` Vincent Legoll
2020-03-26 11:06 ` Ricardo Wurmus
2020-03-26 11:39 ` Pierre Neidhardt
2020-03-27 0:03 ` John Soo
2020-03-26 20:56 ` Christopher Baines
2020-03-27 7:30 ` Pierre Neidhardt
2020-03-27 9:16 ` Christopher Baines
2020-03-27 10:17 ` Pierre Neidhardt
2020-03-27 8:34 ` pinoaffe
2020-03-27 9:42 ` Ricardo Wurmus
2020-03-27 9:59 ` Vincent Legoll
2020-03-27 14:19 ` Ricardo Wurmus
2020-03-27 14:31 ` Vincent Legoll
2020-03-27 18:36 ` pinoaffe
2020-03-28 11:40 ` Vincent Legoll
2020-03-28 22:20 ` Vincent Legoll
2020-03-28 22:20 ` Ricardo Wurmus
2020-03-30 11:07 ` Ricardo Wurmus
2020-03-30 11:33 ` Vincent Legoll
2020-03-29 23:07 ` Björn Höfling
2020-04-01 2:05 ` Ricardo Wurmus
2020-04-06 21:29 ` Björn Höfling
[not found] ` <87blofpii8.fsf@asu.edu>
2020-03-30 8:07 ` Ricardo Wurmus
2020-03-30 21:48 ` John Soo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h7y5v7i5.fsf@asu.edu \
--to=jsoo1@asu.edu \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).