From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/6] npm.bbclass: work with nodejs 16
Date: Thu, 19 May 2022 12:38:50 +0200 [thread overview]
Message-ID: <lybkvtvmbp.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <cover.1652954597.git.enrico.scholz@sigma-chemnitz.de> (Enrico Scholz via lists openembedded org's message of "Thu, 19 May 2022 12:05:50 +0200")
"Enrico Scholz via lists.openembedded.org"
<enrico.scholz=sigma-chemnitz.de@lists.openembedded.org> writes:
> This patchset requires an additional one in the oe-meta layer.
for reference: https://lists.openembedded.org/g/openembedded-devel/message/97186
next prev parent reply other threads:[~2022-05-19 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 10:05 [PATCH 0/6] npm.bbclass: work with nodejs 16 Enrico Scholz
2022-05-19 10:05 ` [PATCH 1/6] npm: replace 'npm pack' call by 'tar czf' Enrico Scholz
2022-05-19 10:25 ` [OE-core] " Zoltan Boszormenyi
2022-05-19 10:05 ` [PATCH 2/6] npm: return content of 'package.json' in 'npm_pack' Enrico Scholz
2022-05-19 10:05 ` [PATCH 3/6] npm: take 'version' directly from 'package.json' Enrico Scholz
2022-05-19 10:05 ` [PATCH 4/6] npm: disable 'audit' + 'fund' Enrico Scholz
2022-05-19 13:56 ` [OE-core] " Luca Ceresoli
2022-05-19 14:06 ` [PATCH 4/6, v2] " Enrico Scholz
2022-05-19 10:05 ` [PATCH 5/6] lib:npm_registry: initial checkin Enrico Scholz
2022-05-19 10:05 ` [PATCH 6/6] npm: use npm_registry to cache package Enrico Scholz
2022-05-19 10:38 ` Enrico Scholz [this message]
2022-05-23 7:23 ` [OE-core] [PATCH 0/6] npm.bbclass: work with nodejs 16 Christian Eggers
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=lybkvtvmbp.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
/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