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/3] package/nodejs: Add version 5.2.0
Date: Mon, 14 Dec 2015 21:09:13 +0100	[thread overview]
Message-ID: <20151214210913.227563c9@free-electrons.com> (raw)
In-Reply-To: <1450122295-5311-1-git-send-email-martin@barkynet.com>

Martin,

On Mon, 14 Dec 2015 19:44:53 +0000, Martin Bark wrote:
> v5.2.0 is the current Stable release. See
> https://nodejs.org/en/blog/release/v5.2.0 for details on the release.
> 
> Signed-off-by: Martin Bark <martin@barkynet.com>

So, we already have 0.10.x, 0.12.x, 4.2.x and now 5.2.x ?

Is it possible to get rid of some older versions, rather than keeping
all of them available ?

Thanks,

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

  parent reply	other threads:[~2015-12-14 20:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 19:44 [Buildroot] [PATCH 1/3] package/nodejs: Add version 5.2.0 Martin Bark
2015-12-14 19:44 ` [Buildroot] [PATCH 2/3] package/nodejs: Fix uClibc-ng support Martin Bark
2015-12-14 19:44 ` [Buildroot] [PATCH 3/3] package/libuv: Fix support for uClibc-ng Martin Bark
2015-12-14 20:09 ` Thomas Petazzoni [this message]
2015-12-14 20:24   ` [Buildroot] [PATCH 1/3] package/nodejs: Add version 5.2.0 Martin Bark
2015-12-14 20:43     ` Thomas Petazzoni
2015-12-14 21:10       ` Yann E. MORIN
2015-12-14 21:31         ` Martin Bark
2015-12-14 21:49           ` Yann E. MORIN
2015-12-14 22:35         ` Jörg Krause
2015-12-16 11:26           ` Vicente Olivert Riera
2015-12-16 13:41             ` Thomas Petazzoni
2015-12-16 16:39               ` Yann E. MORIN
2015-12-17 17:29                 ` Martin Bark
2015-12-17 18:27                   ` Yann E. MORIN
2015-12-17 19:55                     ` Martin Bark
2015-12-17 20:05                       ` Yann E. MORIN

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=20151214210913.227563c9@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