From: Joshua David Williams <yurimxpxman.lkml@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: GPLv3 dispute solution - new open source license?
Date: Mon, 18 Jun 2007 18:07:53 -0400 [thread overview]
Message-ID: <200706181807.53306.yurimxpxman@gmail.com> (raw)
On 6/18/07, Carlo Wood <carlo@alinoe.com> wrote:
> Now, writing yet another license for the linux kernel is
> therefore NOT the solution - if you get my drift.
The new license could be written to be compatible with both versions of the
GPL. IMO, a new license written from the OSS perspective would behoove us
greatly in that we are no longer subject to this Higher Calling of the FSF
and the Church of Emacs.
$0.02
--
It's a commonly known fact that most intruders come in through Windows.
next reply other threads:[~2007-06-18 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 22:07 Joshua David Williams [this message]
2007-06-18 22:43 ` GPLv3 dispute solution - new open source license? david
2007-06-19 2:39 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2007-06-18 21:47 Joshua David Williams
2007-06-18 22:01 ` Carlo Wood
2007-06-18 23:24 ` Alan Cox
2007-06-18 23:22 ` alan
2007-06-18 21:25 Joshua David Williams
2007-06-18 21:38 ` H. Peter Anvin
2007-06-19 21:37 ` Chris Snook
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=200706181807.53306.yurimxpxman@gmail.com \
--to=yurimxpxman.lkml@gmail.com \
--cc=linux-kernel@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