All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/volk: fix licensing information
Date: Sat, 15 Oct 2022 16:32:03 +0200	[thread overview]
Message-ID: <87y1thi2e4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221001213928.6B43A86743@busybox.osuosl.org> (Yann E. MORIN's message of "Sat, 1 Oct 2022 23:35:46 +0200")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > commit: https://git.buildroot.net/buildroot/commit/?id=0a397fa6381a4115be22ee9637746bf8c8e1194e
 > branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

 > Since 2.5.1, volk has been undergoing a relicensing from GPL-3.0+ to the
 > LGPL-3.0+, which is still not completely done 5by some large margin), so
 > it is still covered by the GPL-3.0+, but has parts already covered by
 > the LGPL-3.0+.

 > We so far only listed GPL-3.0+, but we also had the license file for the
 > LGPL-3.0+.

 > Add LGPL-3.0+ to the list of licenses; the COPYING file is the text of
 > the GPL-3.0+, so we already had it listed (note: the package has a
 > COPYING-GPL, but i's a symlink to COPYING).

 > Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
 > [yann.morin.1998@free.fr:
 >   - split out to its own patch
 >   - explain why we don't add COPYING-GPL
 > ]
 > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>

Committed to 2022.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2022-10-15 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01 21:35 [Buildroot] [git commit] package/volk: fix licensing information Yann E. MORIN
2022-10-02 10:06 ` Thomas Petazzoni via buildroot
2022-10-02 12:11   ` Yann E. MORIN
2022-10-15 14:32 ` Peter Korsgaard [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=87y1thi2e4.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.