From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/iojs: new package
Date: Thu, 15 Jan 2015 09:34:27 +0100 [thread overview]
Message-ID: <20150115093427.0b5118b2@free-electrons.com> (raw)
In-Reply-To: <1421278696-15122-1-git-send-email-jkrause@posteo.de>
Dear J?rg Krause,
On Thu, 15 Jan 2015 00:38:16 +0100, J?rg Krause wrote:
> io.js is a fork of Node.js. This package is mainly based on the nodejs
> package, except for the patches.
>
> io.js is currently marked as unstable and there is no stable release for now.
>
> Signed-off-by: J?rg Krause <jkrause@posteo.de>
Immediate question that comes to mind: is the code base diverging from
Node.js ? Do we need two separate packages ? Does this fork has a
chance of becoming widely used ? I'm a bit concerned by the fact of
having two separate packages for basically the same thing.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-01-15 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 23:38 [Buildroot] [PATCH 1/1] package/iojs: new package Jörg Krause
2015-01-15 4:47 ` Baruch Siach
2015-01-15 8:34 ` Thomas Petazzoni [this message]
2015-01-15 19:58 ` Jörg Krause
2015-01-18 16:29 ` Yann E. MORIN
2015-01-20 17:45 ` Jörg Krause
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=20150115093427.0b5118b2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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