From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: Meh Mbeh Ida Delphine <idadelm@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [poky][PATCH v4] Update license file to match current SPDX names
Date: Fri, 16 Oct 2020 11:55:22 +0100 [thread overview]
Message-ID: <4721672db9f150456b07f95af172f65a56445a23.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALbNGRSw_-9XwrsXWt462MeccFKiFCzmVYT4ESLBcitkpFC4Eg@mail.gmail.com>
On Fri, 2020-10-16 at 12:54 +0200, Andreas Müller wrote:
> On Fri, Oct 16, 2020 at 10:42 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Thu, 2020-10-15 at 21:08 +0100, Meh Mbeh Ida Delphine wrote:
> > > Updated mappings of license fields of meta/conf/licenses.conf to
> > > match latest SPDX naming.
> > > Added missing mappings.
> > > Renamed license files that were added in license mappings eg from
> > > GPL-2.0 to GPL-2.0-only.
> Is this intended to go into gatesgarth? As we see from the follow-up
> fixes: This is an incompatible change at feature freeze time.
> Asking this because up to this point I was happy that all my layers
> are working fine on dunfell and master(gatesgarth).
No, I will hold it until after release at this point, its too late to
take a more invasive change like this.
Cheers,
Richard
next prev parent reply other threads:[~2020-10-16 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 20:08 [poky][PATCH v4] Update license file to match current SPDX names Meh Mbeh Ida Delphine
2020-10-16 8:42 ` Richard Purdie
2020-10-16 10:54 ` [OE-core] " Andreas Müller
2020-10-16 10:55 ` Richard Purdie [this message]
2020-10-16 11:32 ` Andreas Müller
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=4721672db9f150456b07f95af172f65a56445a23.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=idadelm@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@gmail.com \
/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