From: Khem Raj <raj.khem@gmail.com>
To: "Marko, Peter" <Peter.Marko@siemens.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH] glibc: correct license
Date: Sun, 5 May 2024 17:12:41 -0700 [thread overview]
Message-ID: <CAMKF1soUDFBKQSXbMuLVo0uFU00G3VOU6F-x38V=ArFkwXvJZA@mail.gmail.com> (raw)
In-Reply-To: <AS1PR10MB569772E4AD10E6FAA803DBDCFD1D2@AS1PR10MB5697.EURPRD10.PROD.OUTLOOK.COM>
On Sun, May 5, 2024 at 1:43 PM Marko, Peter <Peter.Marko@siemens.com> wrote:
>
> From: Khem Raj <raj.khem@gmail.com>
> Sent: Sunday, May 5, 2024 21:22
> To: Marko, Peter (ADV D EU SK BFS1) <Peter.Marko@siemens.com>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core][PATCH] glibc: correct license
>
> > On Sun, May 5, 2024 at 2:18 AM Peter Marko via http://lists.openembedded.org <peter.marko=mailto:siemens.com@lists.openembedded.org> wrote:
> > > From: Peter Marko <mailto:peter.marko@siemens.com>
> > >
> > > The license per https://www.gnu.org/software/libc/ is LGPL-2.1-or-later.
> > > https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=273a835fe7c685cc54266bb8b502787bad5e9bae
> > > converted last LGPL-2.1-only references.
> > >
> > > License-Update: correction
> >
> > This should reflect reason but overall the patch is ok
> >
>
> Could you please be more specific what should I write?
its can be changed/corrected from X to Y then point to supporting
links you have cited as links using [1] [2] etc.
> The long reason is written above the License-Update field, I just added the field to satisfy the patch checker bot.
> Putting the whole text to this field doesn't look right.
>
> I don't know the history of glibc license to be able to assess if they migrated recently or if these were just wrongly committed licenses.
> I just noticed the commit when updating glibc to the latest hash and decided to correct the recipe LICENSE field according to this hint.
> So "correction" looks to me like a good short statement wrt the recipe LICENSE field.
>
> Thanks,
> Peter
prev parent reply other threads:[~2024-05-06 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 9:17 [OE-core][PATCH] glibc: correct license Peter Marko
2024-05-05 19:22 ` Khem Raj
2024-05-05 20:43 ` Marko, Peter
2024-05-06 0:12 ` Khem Raj [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='CAMKF1soUDFBKQSXbMuLVo0uFU00G3VOU6F-x38V=ArFkwXvJZA@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=Peter.Marko@siemens.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).