From: Alex Sassmannshausen <alex@pompo.co>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Generate multiple paginated packages pages.
Date: Thu, 08 Dec 2016 13:02:28 +0100 [thread overview]
Message-ID: <87lgvq1ve3.fsf@pompo.co> (raw)
In-Reply-To: <20161208113648.GA21333@jocasta.intra>
Heya
John Darrington writes:
> On Thu, Dec 08, 2016 at 12:29:22PM +0100, Alex Sassmannshausen wrote:
>
> > Note that I removed the all-in-one package page because the poor CVS
> > server at gnu.org simply can???t handle it.
>
> Sure ??? I figure this way of browsing is more user friendly anyway???
>
> Well yes and no.
>
> It's more friendly in the respect that it no longer takes 2 minutes to load.
>
> But the down side is that I can no longer load the page and then use my
> browser's "Find in Page" button to search for a package---Now I have to
> know what the package is called before I can search for it.
Fair point! I think Luis Felipe is thinking of a more comprehensive
approach to the package pages — mine was more of a quick fix to solve an
urgent problem.
> Maybe sometime in the future a "browse by category" or "search for packages"
> feature will be available?
>
> J'
next prev parent reply other threads:[~2016-12-08 12:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 23:22 [PATCH] Revised generate multiple package pages Alex Sassmannshausen
2016-11-29 23:22 ` [PATCH] Generate multiple paginated packages pages Alex Sassmannshausen
2016-12-04 20:51 ` Ludovic Courtès
2016-12-05 10:16 ` Alex Sassmannshausen
2016-12-08 10:00 ` Ludovic Courtès
2016-12-08 10:54 ` Jan Synáček
2016-12-08 11:29 ` Alex Sassmannshausen
2016-12-08 11:36 ` John Darrington
2016-12-08 12:02 ` Alex Sassmannshausen [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-11 20:03 [PATCH] A patch to generate paginated packages page Alex Sassmannshausen
2016-11-11 20:03 ` [PATCH] Generate multiple paginated packages pages Alex Sassmannshausen
2016-11-12 14:34 ` Ludovic Courtès
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=87lgvq1ve3.fsf@pompo.co \
--to=alex@pompo.co \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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).