unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>
Cc: 22115@debbugs.gnu.org
Subject: bug#22115: (no subject)
Date: Sun, 18 Dec 2016 22:51:28 +0100	[thread overview]
Message-ID: <871sx4oqhr.fsf@gnu.org> (raw)
In-Reply-To: <1566bec1d2fd3ff566c73408c084b5b7@openmailbox.org> ("Luis Felipe López Acevedo"'s message of "Sun, 18 Dec 2016 09:30:42 -0500")

Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:

> On 2016-12-18 05:14, ludo@gnu.org wrote:

[...]

>> Should we just list packages with actual issues?  Or should we add
>> those
>> links?
>
>
> For now, I'd remove the packages without issues. This would help
> reduce the size of the page, which is almost 2 MiB (I use 1 MiB as a
> limit for desktop browsers).

Sounds good.  Would you like to make this change?

> Soon™, I'd like to propose a package pages design where the
> package-list page indicates if a package has issues, and the package
> issues are listed in a package detail page (which does not exist
> yet). The current issues page would disappear. But I'll open a
> separate bug/proposal for this :)

That would be nice!  Looking forward to this.  :-)

Thanks for your feedback,
Ludo’.

  reply	other threads:[~2016-12-18 21:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08  8:39 bug#22115: WWW: Package Issues website has broken CSS Jan Synáček
2016-09-27 16:50 ` bug#22115: ng0
2016-09-27 17:37   ` bug#22115: ng0
2016-09-27 17:53   ` bug#22115: Leo Famulari
2016-11-26  1:12 ` bug#22115: Luis Felipe López Acevedo
2016-12-15  1:36 ` bug#22115: (no subject) Luis Felipe López Acevedo
2016-12-18 10:14   ` Ludovic Courtès
2016-12-18 14:30     ` Luis Felipe López Acevedo
2016-12-18 21:51       ` Ludovic Courtès [this message]
2016-12-20 16:49         ` Luis Felipe López Acevedo
2016-12-17 19:14 ` Luis Felipe López Acevedo

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=871sx4oqhr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=22115@debbugs.gnu.org \
    --cc=felipe.lopez@openmailbox.org \
    /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).