Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 0/2] Fix issue with npm shrinkwrap fetcher
Date: Fri, 5 Feb 2021 01:40:01 +0000	[thread overview]
Message-ID: <8563467700f9308c1de3c1b588a50dff68b7234b.camel@intel.com> (raw)
In-Reply-To: <390151a7-070e-4d1f-2ffe-4051e04e1ab1@pr.hu>

On Wed, 2021-02-03 at 10:55 +0100, Zoltan Boszormenyi via
lists.openembedded.org wrote:
> 2021. 01. 14. 16:40 keltezéssel, Kamel Bouhara írta:
> > On Thu, Jan 14, 2021 at 03:25:50PM +0100, Jean-Marie Lemetayer
> > wrote:
> > > Hi Kamel,
> > > 
> > 
> > Hi Jean-Marie,
> > 
> > > Thanks for your work. I should have fixed this a long time ago
> > > but I
> > > didn't have the time :(
> > > 
> > 
> > Well its never too late !
> > 
> > > There is actually an open bug for this issue:
> > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=13901
> > > I think you can add the reference to your commit messages. And
> > > close
> > > it if merged.
> 
> Please backport this series to Gatesgarth as soon
> as possible because it's a problem there, too.
> The series applies cleanly.

I will pick these for the next pull request.

Thanks,

Anuj

      reply	other threads:[~2021-02-05  1:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  7:12 [PATCH 0/2] Fix issue with npm shrinkwrap fetcher kamel.bouhara
2021-01-14  7:12 ` [PATCH 1/2] npm.bbclass: make shrinkwrap file optional Kamel Bouhara
2021-01-14  7:12 ` [PATCH 2/2] recipetool: create: only add npmsw url if required Kamel Bouhara
2021-01-14 14:25 ` [OE-core] [PATCH 0/2] Fix issue with npm shrinkwrap fetcher Jean-Marie Lemetayer
2021-01-14 15:40   ` Kamel Bouhara
2021-02-03  9:55     ` Zoltan Boszormenyi
2021-02-05  1:40       ` Anuj Mittal [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=8563467700f9308c1de3c1b588a50dff68b7234b.camel@intel.com \
    --to=anuj.mittal@intel.com \
    --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