From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel <guix-devel@gnu.org>
Subject: Re: Switching to ECMAscript
Date: Wed, 02 Apr 2014 15:12:46 +0200 [thread overview]
Message-ID: <87zjk3j2nl.fsf@gnu.org> (raw)
In-Reply-To: <87k3b9l6xs.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 01 Apr 2014 11:45:03 +0200")
[-- Attachment #1: Type: text/plain, Size: 155 bytes --]
Since we failed to reach consensus, I hereby declare that we’ll stick
with Scheme and the functional packaging paradigm.
Foolishly yours,
Ludo’.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2014-04-02 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 9:45 Switching to ECMAscript Ludovic Courtès
2014-04-01 10:02 ` Alex Sassmannshausen
2014-04-01 13:21 ` Ludovic Courtès
2014-04-01 14:07 ` Andreas Enge
2014-04-01 16:17 ` Ludovic Courtès
2014-04-01 18:48 ` Thompson, David
2014-04-01 15:16 ` Felipe López
2014-04-02 13:12 ` 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=87zjk3j2nl.fsf@gnu.org \
--to=ludo@gnu.org \
--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).