From: a.oikonomopoulos@vu.nl (Angelos Oikonomopoulos)
To: cocci@systeme.lip6.fr
Subject: [Cocci] licensing concerns with cocci patches
Date: Wed, 24 Oct 2012 00:18:34 +0200 [thread overview]
Message-ID: <508717BA.2040002@vu.nl> (raw)
In-Reply-To: <alpine.DEB.2.02.1210232339230.1942@localhost6.localdomain6>
On 23/10/2012 11:42 ??, Julia Lawall wrote:
> On Tue, 23 Oct 2012, Angelos Oikonomopoulos wrote:
[...]
>> The concept that the GPL would apply to the output of spatch, just
>> because spatch itself is under the GPL is well beyond far-fetched. By
>> the same logic, it could as well apply to the results of a
>> search-and-replace in emacs :)
>
> Not quite. Because thre is no GPL on the replace. The user writes the
> replace himself. What is being discussed is semantic patches that are
> GPL'd, not the fact that Coccinelle itself is GPL'd.
Oh, I misunderstood the issue in question then, sorry for my careless
reading.
I hope everyone agrees that patches that merely report potential issues
are fine. In the case that a semantic patch adds significant amounts of
original code, it does sound that the authors of the semantic patches
might need to grant an explicit exception. I seriously doubt that the
output of patches like andand.cocci (or any search-and-replace-style
transformation) is copyrightable, however :)
BTW, you might also consider asking the SFLC for pro-bono advice on this
https://www.softwarefreedom.org/about/contact/
HTH,
Aggelos
next prev parent reply other threads:[~2012-10-23 22:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 21:35 [Cocci] licensing concerns with cocci patches Angelos Oikonomopoulos
2012-10-23 21:42 ` Julia Lawall
2012-10-23 22:18 ` Angelos Oikonomopoulos [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-22 16:58 Eitan Adler
2012-10-22 17:05 ` Julia Lawall
2012-10-23 15:04 ` Eitan Adler
2012-10-23 15:18 ` Luis R. Rodriguez
2012-10-23 19:18 ` Julia Lawall
2012-10-23 19:32 ` Eitan Adler
2012-10-23 20:39 ` Julia Lawall
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=508717BA.2040002@vu.nl \
--to=a.oikonomopoulos@vu.nl \
--cc=cocci@systeme.lip6.fr \
/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.