From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/6] taglib: fix legal info
Date: Fri, 31 Mar 2017 09:08:57 +0200 [thread overview]
Message-ID: <87y3vlx6ra.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1490204935-13172-3-git-send-email-rahul.bedarkar@imgtec.com> (Rahul Bedarkar's message of "Wed, 22 Mar 2017 23:18:52 +0530")
>>>>> "Rahul" == Rahul Bedarkar <rahul.bedarkar@imgtec.com> writes:
> taglib is dual licensed under LGPLv2.1 or MPLv1.1. Almost all source
> files have license text mentioning LGPLv2.1 or alternatively MPLv1.1.
> Signed-off-by: Rahul Bedarkar <rahul.bedarkar@imgtec.com>
Committed to 2017.02.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-03-31 7:08 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 [this message]
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 ` [Buildroot] [PATCH 1/6] dbus-glib: fix legal info Thomas Petazzoni
2017-03-31 7:07 ` 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=87y3vlx6ra.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.