From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] gst1-plugins-bad: rework license type construction
Date: Mon, 14 May 2018 08:10:24 +0200 [thread overview]
Message-ID: <20180514081024.525567ea@windsurf.home> (raw)
In-Reply-To: <CANxTyt74dazFq5QO+1mi8ebPnnZx4d2tqWCzdhxM-5YQOONAHA@mail.gmail.com>
Hello,
On Sun, 13 May 2018 22:01:18 -0400, Danomi Manchego wrote:
> > It would be nice to make this vague "GPL" statement a bit clearer. Are
> > we talking about GPL-2.0, GPL-2.0+, GPL-3.0, GPL-3.0+ ? Or a
> > combination of these ?
>
> You mentioned this before. I took action in the second patch in this
> series, http://lists.busybox.net/pipermail/buildroot/2018-May/220939.html
> . In that patch, I updated which plugins were GPL, and changed "GPL"
> to "GPL-2.0+".
Ah, sorry, didn't look at your second patch yet :-/
> As Yann mentioned, I have some proof-reading errors in
> the commit log, so I'll submit a new rev of that second patch.
Yes, I've seen the v2, will have a look. Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-05-14 6:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 19:04 [Buildroot] [PATCH 1/2] gst1-plugins-bad: rework license type construction Danomi Manchego
2018-05-06 19:04 ` [Buildroot] [PATCH 2/2] gst1-plugins-bad: update plugin licenses Danomi Manchego
2018-05-13 21:07 ` Yann E. MORIN
2018-05-24 21:02 ` Peter Korsgaard
2018-05-13 21:04 ` [Buildroot] [PATCH 1/2] gst1-plugins-bad: rework license type construction Yann E. MORIN
2018-05-13 21:22 ` Thomas Petazzoni
2018-05-14 2:01 ` Danomi Manchego
2018-05-14 6:10 ` Thomas Petazzoni [this message]
2018-05-24 21:02 ` Peter Korsgaard
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=20180514081024.525567ea@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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