From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Lint on line
Date: Thu, 03 Dec 2015 12:42:57 +0200 [thread overview]
Message-ID: <87d1unvmmm.fsf@gnu.org> (raw)
In-Reply-To: <20151202085239.GD6872@debian.eduroam.u-bordeaux.fr> (Andreas Enge's message of "Wed, 2 Dec 2015 09:52:39 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> On Wed, Dec 02, 2015 at 08:36:30AM +0100, Jan Synáček wrote:
>> On Tue, Dec 1, 2015 at 11:04 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>> > Initially I left them so that each package at gnu.org/s/guix/packages
>> > could contain a reference to its (possibly empty) issue list (each
>> > package has an anchor in issues.html.)
>> > Do you think that would make sense?
>
> One could drop the link if there are no issues. But that would assume
> that the package list page is aware of the issue page and is recreated
> each time the issue page changes.
Right, and that’s not the case. The pages are built separately; the
package pages is built in seconds, whereas the issue pages is built in
hours.
>> Or maybe one extra button and a tiny piece of javascript to show/hide
>> the no-issue packages?
>
> That sounds like a nice solution. Empty issue list could be of a special
> css class, which would make implementing this easy.
That would be nice. Any takers?
See <http://git.savannah.gnu.org/cgit/guix/guix-artwork.git>.
Thanks,
Ludo’.
prev parent reply other threads:[~2015-12-03 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 23:11 Lint on line Ludovic Courtès
2015-11-23 0:22 ` Leo Famulari
2015-11-23 8:31 ` Alex Kost
2015-11-23 9:46 ` Ludovic Courtès
2015-11-23 9:28 ` Mathieu Lirzin
2015-11-30 18:27 ` Andreas Enge
2015-12-01 22:04 ` Ludovic Courtès
2015-12-02 7:36 ` Jan Synáček
2015-12-02 8:52 ` Andreas Enge
2015-12-03 10:42 ` Ludovic Courtès [this message]
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=87d1unvmmm.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@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 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).