From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Adding build status to the package list table
Date: Sat, 21 Nov 2015 16:36:09 +0100 [thread overview]
Message-ID: <20151121153609.GA9565@thebird.nl> (raw)
In-Reply-To: <878u5rjry5.fsf@gnu.org>
On Sat, Nov 21, 2015 at 04:24:50PM +0100, Roel Janssen wrote:
> > IMO it wouldn’t be very useful since the list is updated once a day.
>
> Ok. If we can instead fetch the status of all packages on all
> architectures in one HTTP request (using javascript on the client-side),
> would that be acceptable? The size of the build status information
> should be about the same size as the list of packages.
>
> For this we need a supporting API call of course.
Sounds good to me as long as it also looks nice for people who switch
JS off.
Pj.
--
next prev parent reply other threads:[~2015-11-21 15:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 12:50 Adding build status to the package list table Roel Janssen
2015-11-19 19:57 ` Mark H Weaver
2015-11-19 21:25 ` Eric Bavier
2015-11-19 22:47 ` Roel Janssen
2015-11-20 16:31 ` Mark H Weaver
2015-11-21 15:21 ` Roel Janssen
2015-11-20 14:18 ` Ludovic Courtès
2015-11-20 16:43 ` Roel Janssen
2015-11-20 21:46 ` Pjotr Prins
2015-11-20 22:49 ` Ludovic Courtès
2015-11-21 15:24 ` Roel Janssen
2015-11-21 15:36 ` Pjotr Prins [this message]
2015-11-21 15:59 ` Ludovic Courtès
2015-11-24 13:24 ` Roel Janssen
2015-11-25 13:56 ` Ludovic Courtès
2015-11-27 0:16 ` Roel Janssen
2016-01-04 20:12 ` Roel Janssen
2016-01-06 16:03 ` Ludovic Courtès
2016-01-06 16:55 ` Roel Janssen
2016-01-06 22:20 ` Ludovic Courtès
2016-02-01 23:23 ` Roel Janssen
2016-02-03 9:28 ` Ludovic Courtès
2016-02-03 9:41 ` Ricardo Wurmus
2016-02-03 10:32 ` Roel Janssen
2016-01-21 10:11 ` Ludovic Courtès
2016-01-21 23:29 ` Roel Janssen
2016-01-22 8:54 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151121153609.GA9565@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=roel@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.