From: Ricardo Wurmus <rekado@elephly.net>
To: gwl-devel@gnu.org
Cc: Malcolm Cook <malcolm.cook@gmail.com>
Subject: Re: FYI: missing image / broken link in header of https://www.guixwl.org/
Date: Sat, 11 May 2019 21:24:32 +0200 [thread overview]
Message-ID: <871s14iykv.fsf@elephly.net> (raw)
In-Reply-To: <CAAAQmVbWEssmT1Cyw9O7WVKJF8S6V2Jo5nUqa8S6Q0-1Un0Z3A@mail.gmail.com>
Hi Malcolm,
> FWIW: it looks unpolished
I totally agree. That’s why I worked on the website some months ago and
hosted it on http://workflows.guix.info with the intention of having the
same thing appear on guixwl.org eventually.
@Roel: would you be willing to have guixwl.org redirect to
workflows.guix.info or workflows.guix.gnu.org? Or could we host it on
the berlin or bayfront servers instead?
--
Ricardo
next prev parent reply other threads:[~2019-05-11 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 17:42 FYI: missing image / broken link in header of https://www.guixwl.org/ Malcolm Cook
2019-05-11 19:24 ` Ricardo Wurmus [this message]
2019-05-14 16:25 ` zimoun
2019-05-14 19:11 ` Ricardo Wurmus
2019-05-14 22:19 ` zimoun
2019-05-15 7:13 ` Ricardo Wurmus
2019-05-14 17:12 ` Roel Janssen
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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871s14iykv.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
--cc=malcolm.cook@gmail.com \
/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.
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).