From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Real-world example for channels?
Date: Tue, 12 Feb 2019 21:41:02 -0800 [thread overview]
Message-ID: <87mun09rf5.fsf@gmail.com> (raw)
In-Reply-To: <87o97hht5m.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 12 Feb 2019 17:24:05 +0100")
[-- Attachment #1: Type: text/plain, Size: 185 bytes --]
Hi Ludo,
I've pushed this as b0a372637f683eae35802af93d67711c3a18e480.
Thank you everyone for the feedback! And thank you to Hartmut for
calling out the problem!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-02-13 5:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 22:16 Real-world example for channels? Hartmut Goebel
2019-01-26 23:00 ` Ricardo Wurmus
2019-01-28 0:46 ` Chris Marusich
2019-01-28 6:57 ` Konrad Hinsen
2019-02-12 16:24 ` Ludovic Courtès
2019-02-13 5:41 ` Chris Marusich [this message]
2019-01-27 9:52 ` Efraim Flashner
2019-01-28 0:49 ` Chris Marusich
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=87mun09rf5.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=help-guix@gnu.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.
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).