From: "Robin Jarry" <rjarry@redhat.com>
To: "Thomas Monjalon" <thomas@monjalon.net>,
"Stephen Hemminger" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] devtools: download scripts from linux if not found
Date: Tue, 26 Nov 2024 16:56:42 +0100 [thread overview]
Message-ID: <D5W8EYO3C7SU.GPJYSDVX8XV7@redhat.com> (raw)
In-Reply-To: <10109280.EvYhyI6sBW@thomas>
Thomas Monjalon, Nov 26, 2024 at 16:36:
> The central question is to know how to get those GPL2 scripts accepted
> in DPDK.
These are scripts, not linked to any DPDK related binary. So I think it
is OK in terms of license contamination. We MUST preserve the original
license headers in these imported scripts though.
I could find this link that discusses the matter:
https://wiki.tcl-lang.org/page/GPL+Scripts
I am not a legal expert though :)
prev parent reply other threads:[~2024-11-26 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-15 14:14 Robin Jarry
2024-10-04 16:31 ` Stephen Hemminger
2024-11-26 14:03 ` Thomas Monjalon
2024-11-26 15:16 ` Robin Jarry
2024-11-26 15:36 ` Thomas Monjalon
2024-11-26 15:56 ` Robin Jarry [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=D5W8EYO3C7SU.GPJYSDVX8XV7@redhat.com \
--to=rjarry@redhat.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.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;
as well as URLs for NNTP newsgroup(s).