openembedded-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Böszörményi Zoltán" <zboszor@pr.hu>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-oe][PATCH] nodejs: Upgrade to 16.11.1
Date: Wed, 2 Mar 2022 07:59:16 -0800	[thread overview]
Message-ID: <CAMKF1srf1707vBB_SnmTUcK4JUAmJOD7QYDq4D+A6XQZur5LVg@mail.gmail.com> (raw)
In-Reply-To: <6b1ef880-a75b-80b1-63f9-f91f88353200@pr.hu>

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

On Tue, Mar 1, 2022 at 11:13 PM Böszörményi Zoltán <zboszor@pr.hu> wrote:

> 2022. 03. 01. 18:12 keltezéssel, Khem Raj írta:
> >
> >
> > On 3/1/22 5:35 AM, Böszörményi Zoltán wrote:
> >> 2021. 10. 21. 0:52 keltezéssel, Khem Raj írta:
> >>> * This is new LTS release
> >>
> >> 16.14.0 is released since then, and 16.x is the LTS series.
> >> Can you please upgrade the recipe?
> >
> > Currently, drowned in making meta-oe layers build. Perhaps it will
> happen after that,
> > unless someone beats me to it.
>
> Would you accept a patch to add into Kirkstone?


Kirkstone is not branch yet so yes

>
>
> >
> >>
> >> Thanks in advance.
>
>

[-- Attachment #2: Type: text/html, Size: 1208 bytes --]

  parent reply	other threads:[~2022-03-02 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 22:52 [meta-oe][PATCH] nodejs: Upgrade to 16.11.1 Khem Raj
     [not found] ` <5a6ea84f-a5cc-25cf-a917-db3cd3c810f2@pr.hu>
     [not found]   ` <25148490-0b41-de90-c014-2d2856de8950@gmail.com>
     [not found]     ` <6b1ef880-a75b-80b1-63f9-f91f88353200@pr.hu>
2022-03-02 15:59       ` Khem Raj [this message]
     [not found]         ` <9aa32d19-b412-472e-b02e-194397331b10@pr.hu>
2022-03-03  6:51           ` [oe] " Khem Raj
2022-03-04 13:46             ` Valek, Andrej

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=CAMKF1srf1707vBB_SnmTUcK4JUAmJOD7QYDq4D+A6XQZur5LVg@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=zboszor@pr.hu \
    /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;
as well as URLs for NNTP newsgroup(s).