all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Sassmannshausen <alex@pompo.co>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "Luis Felipe López Acevedo" <felipe.lopez@openmailbox.org>,
	25045@debbugs.gnu.org
Subject: bug#25045: [Website] Packages page takes too long to load
Date: Mon, 28 Nov 2016 18:00:33 +0100	[thread overview]
Message-ID: <87inr7pmj2.fsf@pompo.co> (raw)
In-Reply-To: <878ts4jz8m.fsf@gnu.org>

Hi Luis,

Indeed, I had a first bash at solving this problem by providing a set of
static html pages paginated by the first letter of the package name.

I'm not particularly wedded to this solution, so if you feel strongly
about going another way, I'd be keen to hear/see about it.

In the meantime, I'm open to testing/feedback.  I will unfortunately not
be able to put work into this until at least Saturday/Sunday, as some
Perl work has higher priority at the moment.

But let me know if you have questions or feedback!

Best wishes,

Alex

Ludovic Courtès writes:

> Hello!
>
> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>
>> I plan to redesign the packages page, and submit a proposal to fix
>> this bug.
>
> For the record, Alex (Cc’d) posted an initial patch a week ago:
>
>   https://lists.gnu.org/archive/html/guix-devel/2016-11/msg00498.html
>
> Please coordinate.  :-)
>
> Glad to see people working on this longstanding issue!
>
> Ludo’.

  reply	other threads:[~2016-11-28 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27 19:19 bug#25045: [Website] Packages page takes too long to load Luis Felipe López Acevedo
2016-11-27 23:10 ` Ludovic Courtès
2016-11-28 17:00   ` Alex Sassmannshausen [this message]
2016-11-28 18:41     ` Luis Felipe López Acevedo
2016-11-28 20:18       ` Ludovic Courtès
2016-11-29  9:12         ` Alex Sassmannshausen
2016-12-09 22:40           ` Ludovic Courtès
2016-12-02 22:41         ` ng0

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87inr7pmj2.fsf@pompo.co \
    --to=alex@pompo.co \
    --cc=25045@debbugs.gnu.org \
    --cc=felipe.lopez@openmailbox.org \
    --cc=ludo@gnu.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.