From: Rahul Bedarkar <Rahul.Bedarkar@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] elfutils: clarify licensing info
Date: Wed, 5 Oct 2016 12:16:49 +0530 [thread overview]
Message-ID: <57F4A1D9.9060408@imgtec.com> (raw)
In-Reply-To: <798633b6-2ff6-45d4-ad74-be9702c1ea4b@free-electrons.com>
Hello,
On Wednesday 05 October 2016 04:36 AM, Gustavo Zacarias wrote:
>>> +ELFUTILS_LICENSE += GPLv3+ (programs)
>>
>> Since it is separate component, it should be comma separated.
>>
>> ELFUTILS_LICENSE := $(ELFUTILS_LICENSE), GPLv3+ (programs)
>
> Most packages don't do this correctly, only a few do and i've used those
> as example, though it's no excuse. Care to fix the others?
I will add it to my todo list.
Thanks,
Rahul
prev parent reply other threads:[~2016-10-05 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 10:44 [Buildroot] [PATCH] elfutils: clarify licensing info gustavo.zacarias at free-electrons.com
2016-10-04 13:01 ` Rahul Bedarkar
2016-10-04 23:06 ` Gustavo Zacarias
2016-10-05 6:46 ` Rahul Bedarkar [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=57F4A1D9.9060408@imgtec.com \
--to=rahul.bedarkar@imgtec.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