Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/nodejs: bump version to 0.10.44
Date: Tue, 26 Apr 2016 21:59:15 +0200	[thread overview]
Message-ID: <20160426215915.7ac3d838@free-electrons.com> (raw)
In-Reply-To: <1461666538-32692-1-git-send-email-martin@barkynet.com>

Hello,

On Tue, 26 Apr 2016 11:28:57 +0100, Martin Bark wrote:
> See https://nodejs.org/en/blog/release/v0.10.44/
> 
> Signed-off-by: Martin Bark <martin@barkynet.com>
> ---
>  .../{0.10.43 => 0.10.44}/0001-remove-python-bz2-dependency.patch      | 0
>  .../{0.10.43 => 0.10.44}/0002-gyp-force-link-command-to-use-CXX.patch | 0
>  .../{0.10.43 => 0.10.44}/0003-fix-musl-USE-MISC-build-issue.patch     | 0
>  .../nodejs/{0.10.43 => 0.10.44}/0004-Fix-support-for-uClibc-ng.patch  | 0
>  package/nodejs/Config.in                                              | 2 +-
>  package/nodejs/nodejs.hash                                            | 4 ++--
>  6 files changed, 3 insertions(+), 3 deletions(-)
>  rename package/nodejs/{0.10.43 => 0.10.44}/0001-remove-python-bz2-dependency.patch (100%)
>  rename package/nodejs/{0.10.43 => 0.10.44}/0002-gyp-force-link-command-to-use-CXX.patch (100%)
>  rename package/nodejs/{0.10.43 => 0.10.44}/0003-fix-musl-USE-MISC-build-issue.patch (100%)
>  rename package/nodejs/{0.10.43 => 0.10.44}/0004-Fix-support-for-uClibc-ng.patch (100%)

Both applied to master, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2016-04-26 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 10:28 [Buildroot] [PATCH 1/2] package/nodejs: bump version to 0.10.44 Martin Bark
2016-04-26 10:28 ` [Buildroot] [PATCH 2/2] package/nodejs: bump version to 5.11.0 Martin Bark
2016-04-26 19:59 ` 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=20160426215915.7ac3d838@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