From: Vincent Legoll <vincent.legoll@gmail.com>
To: pinoaffe@airmail.cc
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Brainstorming features for issues.guix.gnu.org
Date: Sat, 28 Mar 2020 23:20:44 +0100 [thread overview]
Message-ID: <CAEwRq=psHTtJBBHeN=D9v2tX_JqOsbf9ru+SYDOFjsErdbiUow@mail.gmail.com> (raw)
In-Reply-To: <CAEwRq=oOFJanC9ySYwoFW-3o0ykfS_wfAvRyE1Y5-4KBLhESDw@mail.gmail.com>
Another feature idea...
I often use it to educate myself on what's going
on and read status about various things.
When doing so I do not always want to scroll
through kilometers of patches.
A way to collapse / hide all/too big patches on
an issue page would be great, to enhance
readability
--
Vincent Legoll
next prev parent reply other threads:[~2020-03-28 22:20 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 [this message]
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
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='CAEwRq=psHTtJBBHeN=D9v2tX_JqOsbf9ru+SYDOFjsErdbiUow@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=pinoaffe@airmail.cc \
/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).