From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] license situation and OSI
Date: Wed, 26 May 2010 08:03:19 -0400 [thread overview]
Message-ID: <FBDEF3CA-971E-4AFF-A80D-48A3D577DE9E@9srv.net> (raw)
In-Reply-To: <80a3558f-c291-4770-9945-57c3a3fbd15f@c22g2000vbb.googlegroups.com>
> Does this mean that for all intents and purposes, Plan9 can be
> considered EPL (even if licence notices say otherwise)?
The short answer is "no". You don't get to change the license, even if
you or some other body decide the terms are equivelent in some way.
You're given the software under the terms of the current LPL, period.
anthony
>
next prev parent reply other threads:[~2010-05-26 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 8:37 staalmannen
2010-05-26 9:55 ` EBo
2010-05-26 12:03 ` Anthony Sorace [this message]
2010-05-26 12:42 ` Charles Forsyth
2010-05-26 15:57 ` Jack Johnson
2010-05-26 17:24 ` Nick LaForge
2010-05-26 19:57 ` Jack Johnson
2010-05-26 20:08 ` Corey
2010-05-26 20:28 ` Jack Johnson
2010-05-26 20:42 ` Corey
2010-05-27 3:10 ` Anthony Sorace
2010-05-26 18:50 ` Russ Cox
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=FBDEF3CA-971E-4AFF-A80D-48A3D577DE9E@9srv.net \
--to=a@9srv.net \
--cc=9fans@9fans.net \
/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).