From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] dbus-glib: fix legal info
Date: Sun, 26 Mar 2017 22:51:35 +0200 [thread overview]
Message-ID: <20170326225135.5fe7a6dd@free-electrons.com> (raw)
In-Reply-To: <1490204935-13172-1-git-send-email-rahul.bedarkar@imgtec.com>
Hello,
On Wed, 22 Mar 2017 23:18:50 +0530, Rahul Bedarkar wrote:
> dbus glib bindings are dual licensed under AFLv2.1 or GPLv2+.
> Separate licenses using 'or' keyword.
>
> Signed-off-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com>
> ---
> package/dbus-glib/dbus-glib.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Patches 1 to 3 applied. On PATCH 3, I've changed MPLv1.1 to MPL-1.1, to
match the SPDX license code.
As discussed previously, I've dropped patches 4 to 6, since we really
want to use the SPDX license codes.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-26 20:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 17:48 [Buildroot] [PATCH 1/6] dbus-glib: fix legal info Rahul Bedarkar
2017-03-22 17:48 ` [Buildroot] [PATCH 2/6] dbus-triggerd: add license file Rahul Bedarkar
2017-03-31 7:08 ` Peter Korsgaard
2017-03-22 17:48 ` [Buildroot] [PATCH 3/6] taglib: fix legal info Rahul Bedarkar
2017-03-31 7:08 ` Peter Korsgaard
2017-03-22 17:48 ` [Buildroot] [PATCH 4/6] python-mwscrape: use documented license abbreviation Rahul Bedarkar
2017-03-22 20:39 ` Thomas Petazzoni
2017-03-22 22:32 ` Yann E. MORIN
2017-03-23 8:25 ` Arnout Vandecappelle
2017-03-23 9:00 ` Thomas Petazzoni
2017-03-23 18:01 ` Rahul Bedarkar
2017-03-28 6:44 ` Peter Korsgaard
2017-03-22 17:48 ` [Buildroot] [PATCH 5/6] python-certifi: " Rahul Bedarkar
2017-03-22 17:48 ` [Buildroot] [PATCH 6/6] perl-encode-detect: " Rahul Bedarkar
2017-03-26 20:51 ` Thomas Petazzoni [this message]
2017-03-31 7:07 ` [Buildroot] [PATCH 1/6] dbus-glib: fix legal info 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=20170326225135.5fe7a6dd@free-electrons.com \
--to=thomas.petazzoni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox