From: Jaap Crezee <jaap@jcz.nl>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/nodejs: bump version to 4.2.2
Date: Mon, 23 Nov 2015 18:34:31 +0100 [thread overview]
Message-ID: <56534E27.7050408@jcz.nl> (raw)
In-Reply-To: <1448228400-25407-1-git-send-email-martin@barkynet.com>
Hi Martin,
On 11/22/15 22:40, Martin Bark wrote:
> v4.2.2 is the current Long Term Support (LTS) version
Agree, would be nice to have that in BR.
> Moved all v4.1.2 patches to v4.2.2 except 0004-fix-arm-vfpv2.patch as this
> is no longer needed. Instead use the new --with-arm-fpu configure option.
> See https://github.com/nodejs/node/issues/2942 and
> https://github.com/nodejs/node/pull/3228.
>
> Also, with the introduction of --with-arm-fpu rename NODEJS_ARM_FP to
> NODEJS_ARM_FLOAT_ABI to make nodejs.mk more readable.
>
> Signed-off-by: Martin Bark <martin@barkynet.com>
This looks good (not tested yet, will do wednesday), however: I think BR would also
benefit on a global level for something like this. Something like that was hinted in one
of the previous nodejs emails.
regards,
Jaap
prev parent reply other threads:[~2015-11-23 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 21:40 [Buildroot] [PATCH 1/1] package/nodejs: bump version to 4.2.2 Martin Bark
2015-11-23 17:34 ` Jaap Crezee [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56534E27.7050408@jcz.nl \
--to=jaap@jcz.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.