From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/7] package/nodejs: bump version to 5.3.0
Date: Fri, 25 Dec 2015 18:49:34 +0100 [thread overview]
Message-ID: <20151225184934.01e38196@free-electrons.com> (raw)
In-Reply-To: <CAFGQKxcXS3CL9VC01SxWrbdstPJzP+ruWf+H58u0PNm0-L5epA@mail.gmail.com>
Martin,
On Thu, 24 Dec 2015 16:16:07 +0000, Martin Bark wrote:
> > I've applied patches 1, 2, 3, 4, 6 and 7. I've left out patch 5 because
> > I have some concerns about it. I'll reply to patch 5 with some details.
>
> Thanks for that. It does not look like patch 3 "package/nodejs:
> correct 0.10.x option name" got applied, is there a reason?
Absolutely my bad. I just applied it now.
Thanks for spotting the issue!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-12-25 17:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 12:16 [Buildroot] [PATCH v3 1/7] package/nodejs: bump version to 5.3.0 Martin Bark
2015-12-23 12:16 ` [Buildroot] [PATCH v3 2/7] package/nodejs: removed version 0.12.9 Martin Bark
2015-12-23 12:16 ` [Buildroot] [PATCH v3 3/7] package/nodejs: correct 0.10.x option name Martin Bark
2015-12-23 12:16 ` [Buildroot] [PATCH v3 4/7] package/nodejs: fixed comment for mips soft float Martin Bark
2015-12-23 12:16 ` [Buildroot] [PATCH v3 5/7] package/nodejs: remove version choice Martin Bark
2015-12-23 17:56 ` Thomas Petazzoni
2015-12-23 18:26 ` Yann E. MORIN
2015-12-24 16:23 ` Martin Bark
2015-12-30 0:09 ` Arnout Vandecappelle
2015-12-23 12:16 ` [Buildroot] [PATCH v3 6/7] package/nodejs: fix support for uClibc-ng Martin Bark
2015-12-23 12:16 ` [Buildroot] [PATCH v3 7/7] package/libuv: " Martin Bark
2015-12-23 17:54 ` [Buildroot] [PATCH v3 1/7] package/nodejs: bump version to 5.3.0 Thomas Petazzoni
2015-12-24 16:16 ` Martin Bark
2015-12-25 17:49 ` Thomas Petazzoni [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=20151225184934.01e38196@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