From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] licensing concerns with cocci patches
Date: Mon, 22 Oct 2012 19:05:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1210221902220.3683@hadrien> (raw)
In-Reply-To: <CAF6rxgkr4aQ-b8HpxJ9w8FMOTL63w7GFJqF5FD5MOwaJ3Kni5w@mail.gmail.com>
On Mon, 22 Oct 2012, Eitan Adler wrote:
> Hi,
>
> I am interested in adding cocci scripts to the FreeBSD tree as a suite
> of scripts that can be used to help find bugs. I have some concerns
> about the license of the "semantic patches" I found. In particular
> quite a few of them are GPLv2 (andand.cocci, ifaddr.cocci,
> isnull.cocci, etc). Ordinarily the product of GPL software isn't GPLed
> but these seem different as the result is merely a transformation of
> patch template.
>
> Is the output of spatch + a GPL semantic patch GPL or can we license
> it under a free software license?
My understanding is that the output of a semantic patch should not be GPL.
But I am not an expert. In any case, that is the intent. We would
certainly be happy that the scripts be part of BSD.
julia
next prev parent reply other threads:[~2012-10-22 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 16:58 [Cocci] licensing concerns with cocci patches Eitan Adler
2012-10-22 17:05 ` Julia Lawall [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2012-10-23 21:35 Angelos Oikonomopoulos
2012-10-23 21:42 ` Julia Lawall
2012-10-23 22:18 ` Angelos Oikonomopoulos
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=alpine.DEB.2.02.1210221902220.3683@hadrien \
--to=julia.lawall@lip6.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox