From: Dan Carpenter <error27@gmail.com>
To: linux-sparse@vger.kernel.org
Subject: relicensing Sparse
Date: Thu, 11 Aug 2011 01:08:06 +0300 [thread overview]
Message-ID: <20110810220806.GD3777@shale.localdomain> (raw)
All of you probably know that I've been contacting people to try get
permission to relicense Sparse to the MIT license. The Transmeta
code was relicensed some years ago but we needed to collect all
the copyright holders to do a full relicense. I basically did a git
blame and if you have over 10 lines of Sparse code, then I sent you
an email.
I havent' been able to reach these two people:
Luc Van Oostenryck <luc.vanoostenryck@looxix.net> (279 lines)
Richard Knutsson <ricknu-0@student.ltu.se> (21 lines)
Does anyone know how I can reach them? Are they on this list?
I'm also waiting to hear back from two people, but hopefully we
should be able to finish relicensing fairly soon.
regards,
dan carpenter
next reply other threads:[~2011-08-10 22:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 22:08 Dan Carpenter [this message]
2011-08-10 23:09 ` relicensing Sparse Josh Triplett
2011-08-11 10:39 ` Dan Carpenter
2011-08-11 20:49 ` Josh Triplett
2011-08-11 22:47 ` Christopher Li
2011-08-11 22:52 ` Dan Carpenter
[not found] <20110226173414.GN18043@bicker>
2011-02-26 18:10 ` Alexey Dobriyan
2011-02-26 18:24 ` Dan Carpenter
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=20110810220806.GD3777@shale.localdomain \
--to=error27@gmail.com \
--cc=linux-sparse@vger.kernel.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 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.