From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/6] gst-plugins-bad: add legal info
Date: Thu, 19 Nov 2015 19:08:52 -0300 [thread overview]
Message-ID: <564E4874.30501@free-electrons.com> (raw)
In-Reply-To: <564CF5A5.1080207@mind.be>
On 18/11/15 19:03, Arnout Vandecappelle wrote:
> comma-separated, I would drop the v2, I would also put LGPL first because it is
> dominant, and perhaps explicitly state which ones are GPLv2+:
>
> GST_PLUGINS_BAD_LICENSE = LGPLv2.1+, GPLv2+ (debugutils,mpegpsmux, mpegtsmux, \
> librfb, audiovisualizers, tta, dvb, vdpau)
>
> but maybe that's too much...
>
> Regards,
> Arnout
Hi Arnout.
ACK, though i'll skip the gory details and go for simple.
Regards.
next prev parent reply other threads:[~2015-11-19 22:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 12:39 [Buildroot] [PATCH 1/6] gstreamer: add legal info gustavo.zacarias at free-electrons.com
2015-11-18 12:39 ` [Buildroot] [PATCH 2/6] gst-plugins-base: " gustavo.zacarias at free-electrons.com
2015-11-18 21:49 ` Arnout Vandecappelle
2015-11-18 12:39 ` [Buildroot] [PATCH 3/6] gst-plugins-good: " gustavo.zacarias at free-electrons.com
2015-11-18 21:53 ` Arnout Vandecappelle
2015-11-18 12:39 ` [Buildroot] [PATCH 4/6] gst-plugins-bad: " gustavo.zacarias at free-electrons.com
2015-11-18 22:03 ` Arnout Vandecappelle
2015-11-19 22:08 ` Gustavo Zacarias [this message]
2015-11-18 12:39 ` [Buildroot] [PATCH 5/6] gst-plugins-ugly: " gustavo.zacarias at free-electrons.com
2015-11-18 22:12 ` Arnout Vandecappelle
2015-11-19 22:06 ` Gustavo Zacarias
2015-11-20 21:27 ` Arnout Vandecappelle
2015-11-18 12:39 ` [Buildroot] [PATCH 6/6] gst-ffmpeg: " gustavo.zacarias at free-electrons.com
2015-11-18 22:15 ` Arnout Vandecappelle
2015-11-18 21:40 ` [Buildroot] [PATCH 1/6] gstreamer: " Arnout Vandecappelle
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=564E4874.30501@free-electrons.com \
--to=gustavo.zacarias@free-electrons.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 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.