From: David Given <dg@cowlark.com>
To: linux-sparse@vger.kernel.org
Subject: sparse licensing query
Date: Sat, 12 Jul 2008 00:02:19 +0100 [thread overview]
Message-ID: <4877E67B.9040106@cowlark.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
I'm just putting together some documentation in preparation for a proper
release of Clue, and have been doing some license paperwork (I want to
properly attribute sparse). I notice that the LICENSE documentation
refers to the OSL v1.1 (and provides a dead link to www.opensource.com).
Given that the OSL is now at v3.0, does sparse use OSL v1.1 on purpose
or simply that nobody got round to updating it?
(I also note, purely for informational value, that no version of the OSL
is DSFG compatible.)
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│ "I have always wished for my computer to be as easy to use as my
│ telephone; my wish has come true because I can no longer figure out
│ how to use my telephone." --- Bjarne Stroustrup
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next reply other threads:[~2008-07-11 23:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 23:02 David Given [this message]
2008-07-12 0:00 ` sparse licensing query Josh Triplett
2008-07-20 23:17 ` H. Peter Anvin
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=4877E67B.9040106@cowlark.com \
--to=dg@cowlark.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 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).