From: Dan Carpenter <error27@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-sparse@vger.kernel.org, Josh Triplett <josh@kernel.org>
Subject: Re: Novafora relicenses Transmeta sparse copyrights under the MIT license
Date: Wed, 9 Feb 2011 22:41:51 +0300 [thread overview]
Message-ID: <AANLkTim3MRfHFRWqx2NuvpXrZ2MCoWwkyzX58tF-Paq6@mail.gmail.com> (raw)
In-Reply-To: <70318cbf0904170316v290edcfag2ac62a15a7254259@mail.gmail.com>
I really would like to relicense Smatch. Probably to GPL v2 or
higher. What's the status of the Sparse relicensing? Is anyone
working on this? Should I start emailing people to get individual
sign-offs on using the MIT license?
regards,
dan carpenter
next prev parent reply other threads:[~2011-02-09 19:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 22:49 Novafora relicenses Transmeta sparse copyrights under the MIT license H. Peter Anvin
2009-04-15 0:06 ` Linus Torvalds
2009-04-15 12:25 ` Alexey Zaytsev
2009-04-16 5:32 ` David Given
2009-04-17 10:16 ` Christopher Li
2011-02-09 19:41 ` Dan Carpenter [this message]
2011-02-09 20:05 ` H. Peter Anvin
2011-02-09 20:06 ` H. Peter Anvin
2013-11-06 16:14 ` Schrober
2013-11-06 17:16 ` H. Peter Anvin
2013-11-06 19:40 ` Christopher Li
2013-11-07 9:46 ` Schrober
2013-11-07 10:01 ` Dan Carpenter
2013-11-07 11:04 ` Michael Stefaniuc
2013-11-07 16:18 ` Randy Dunlap
[not found] ` <20131107212415.GV26669@mwanda>
2013-11-08 16:13 ` Schrober
2013-11-08 16:21 ` Frederic Crozat
2013-11-08 16:35 ` Peter Jones
2013-11-08 17:13 ` Pekka Enberg
2013-11-08 17:27 ` Dan Carpenter
2013-11-14 23:33 ` Jan Pokorný
2013-11-08 18:00 ` Dan Carpenter
2013-11-09 8:23 ` Schrober
2013-11-09 8:27 ` Joe Perches
2013-11-09 19:42 ` Adam DiCarlo
[not found] ` <CANeU7QmPf-ELk7b1C5AZ6xU7Rns2-ZR9VYCdVG8FTHi43Kopig@mail.gmail.com>
2013-11-11 3:58 ` Christopher Li
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=AANLkTim3MRfHFRWqx2NuvpXrZ2MCoWwkyzX58tF-Paq6@mail.gmail.com \
--to=error27@gmail.com \
--cc=hpa@zytor.com \
--cc=josh@kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
/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).